googleapis/mcp-toolbox · error
description is required for tool %q
Error message
description is required for tool %q
What it means
Thrown by Config.Initialize when the cloudhealthcare-get-dicom-store-metrics tool is defined with an empty Description. A description is mandatory so MCP clients can display the tool's purpose. Initialization aborts before the tool is registered.
Source
Thrown at internal/tools/cloudhealthcare/cloudhealthcaregetdicomstoremetrics/cloudhealthcaregetdicomstoremetrics.go:69
}
type Config struct {
tools.ConfigBase `yaml:",inline"`
Type string `yaml:"type" validate:"required"`
Source string `yaml:"source" validate:"required"`
Annotations *tools.ToolAnnotations `yaml:"annotations,omitempty"`
}
// validate interface
var _ tools.ToolConfig = Config{}
func (cfg Config) ToolConfigType() string {
return resourceType
}
func (cfg Config) Initialize(context.Context) (tools.Tool, error) {
if cfg.Description == "" {
return nil, fmt.Errorf("description is required for tool %q", cfg.Name)
}
params := buildParams(false)
return Tool{
BaseTool: tools.NewBaseTool(
cfg,
tools.GetAnnotationsOrDefault(cfg.Annotations, tools.NewReadOnlyAnnotations),
tools.Manifest{Description: cfg.Description, Parameters: params.Manifest(), AuthRequired: cfg.AuthRequired},
params,
),
}, nil
}
// validate interface
var _ tools.Tool = Tool{}
type Tool struct {
tools.BaseTool[Config]View on GitHub (pinned to 8cc6e09de2)
Solutions
- Add a non-empty description to the tool's YAML config
- Set cfg.Description before Initialize
- Add startup validation to surface missing descriptions early
Example fix
# before kind: cloud-healthcare-get-dicom-store-metrics # after kind: cloud-healthcare-get-dicom-store-metrics description: Fetches metrics for a DICOM store in Cloud Healthcare
Defensive patterns
Strategy: validation
Validate before calling
if cfg.Description == "" {
return fmt.Errorf("tool %q requires a description", cfg.Name)
} Prevention
- Document the description field as mandatory in tool templates
- Add a config linter for empty description strings
- Review YAML diffs for dropped fields
When it happens
Trigger: Calling Initialize on a Config with Description == "" (field omitted in YAML or left unset in code).
Common situations: Missing description key in the tool YAML; generating configs from templates that skip optional-looking fields; empty-string description from automation.
Related errors
- description is required for tool %q
- description is required for tool %q
- description is required for tool %q
- description is required for tool %q
- description is required for tool %q
AI-assisted analysis of googleapis/mcp-toolbox@8cc6e09de2 (2026-09-05).
Data as JSON: /api/errors/00a932b28c5f8222.
Report an issue: GitHub.