Get UNICEF Indicator Temporal Coverage

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false. The description adds behavioral traits: 'fetches a small sample', 'lightweight — does not fetch all observations', which aligns with annotations and provides extra context. No 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?

Three sentences, no redundant words. Efficiently communicates purpose, behavior, and usage guidance. Front-loaded with key action, then lightweight hint, then usage advice.

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 simplicity (single parameter, output schema exists), the description is complete. It explains what the tool does, how it behaves, and when to use it relative to siblings. No missing information for effective selection.

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%, and the schema provides detailed description for the single parameter 'code'. The tool description does not add parameter-specific detail beyond what the schema offers, but baseline 3 is appropriate given high schema coverage.

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 it checks what years of data are available for a UNICEF indicator, with specific verbs ('Check', 'Fetches') and resource ('temporal coverage'). It distinguishes itself from sibling 'get_data' by advising to use it before get_data to pick a year range.

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?

Provides explicit usage context: 'Use before get_data() to pick a year range.' Also notes it is lightweight and does not fetch all observations, implying when to prefer this tool over get_data. Could be improved by mentioning when not to use it, but current guidance is clear.

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