get_eu_gdp

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds key behavioral traits: data is cached for 24 hours, missing periods are omitted (not returned as null), and typical Eurostat data lag is 60-90 days. This provides rich context beyond annotations.

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?

The description is well-structured with a clear opening sentence stating the tool's purpose. It then covers output format, defaults, caching, and usage in a logical order. While it is detailed, every sentence serves a purpose; minor verbosity could be trimmed.

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?

Given the absence of an output schema, the description thoroughly explains the returned data structure (array of objects with country, period, value, unit), plus source and retrieved_at fields. It covers all parameters, default behavior, caching, data lag, and missing period handling. Complete for a data retrieval tool.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the semantic meaning of each unit (e.g., CLV_PCH_SM for year-on-year growth) and giving examples of country codes (EA20, EU27_2020). It also clarifies defaults and parameter effects.

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?

The description clearly states the tool fetches quarterly GDP data for EU/Eurozone countries from Eurostat, specifying the dataset (namq_10_gdp). It distinguishes from siblings which cover other economic indicators like inflation, unemployment, and exchange rates.

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?

The description includes explicit guidance on when to use each unit parameter (e.g., use CLV_PCH_SM for cross-country growth comparisons, CP_MEUR for absolute GDP size). It also mentions typical data lag and suggests using more quarters for recession analysis. However, it does not directly compare with sibling tools.

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