get_series_group

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds value by specifying the exact return fields (title, region type, units, frequency, span), which goes beyond what annotations provide. No behavioral contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, well-structured sentence with front-loaded key information. Every word adds value; no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one required parameter, high schema coverage, and an output schema, the description is entirely sufficient. It covers the tool's purpose, input, and output comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear description and example for series_id. Description adds context by explaining that the parameter must be a regional series_id and that the response depends on it, including a list of output fields. This is above the baseline of 3 because the description enriches understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb (fetch), resource (series-group metadata), and scope (for a regional series). Distinguishes from siblings by explicitly mentioning 'GeoFRED / Maps' and 'regional series', which sets it apart from general series tools like get_series_data or get_series.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes what input to provide (a regional series_id) and what output to expect (group metadata). While not explicitly stating when not to use it or naming alternatives, the context of 'regional series' implicitly guides the agent to use this instead of general series tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.