get_eu_inflation

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. Description adds significant behavioral details: data is cached for 24 hours, typical data lag is 30-45 days, and output structure is JSON with specific fields. No contradictions with annotations. Adds valuable context beyond what annotations provide.

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?

Description is well-structured: first sentence explains core function, then output format, defaults, caching, usage guidelines, and additional tips. Every sentence serves a purpose with no fluff. Length is appropriate given the complexity.

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 tool's moderate complexity and simple schema (2 parameters, no nested objects, no output schema), the description fully covers what an agent needs: data source, output structure, default behavior, caching, data lag, and usage recommendations. Complete enough for correct invocation.

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 descriptions for both parameters (countries and periods). Description adds value by explaining that omitting countries returns all EU members, and provides usage examples for EA and EU27_2020. Also mentions that periods=12 gives 12-month trend. While schema already covers defaults, description reinforces and adds context.

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?

Description clearly states it fetches HICP annual inflation rates for EU countries from Eurostat, specifying the dataset code. The verb 'Fetches' and resource 'HICP annual inflation rates' are specific, and it is distinct from sibling tools like get_ecb_rates or get_eu_gdp which cover different economic indicators.

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?

Explicit guidance on when to use: 'HICP is the EU-harmonised inflation standard used by the ECB for monetary policy — use it (not national CPI) for cross-country comparisons.' Also explains typical data lag, how to retrieve trends with periods=12, and recommends pairing with get_ecb_rates for context. Clearly states when to use vs alternatives.

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