OECD SDMX data query

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

Discloses return format (SDMX-JSON), explains key wildcard syntax, and offers performance optimization tips. Adds value beyond annotations (readOnlyHint, idempotentHint) by detailing behavior.

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?

Two efficient sentences plus parameter examples. Front-loaded with purpose, no wasted words.

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?

Covers main parameters and gives usage guidance. Lacks explanation of return structure or error handling, but adequate for a query tool with strong annotations.

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?

Adds meaning beyond schema: provides format and examples for dataflow and key, gives examples for startPeriod/endPeriod, explains lastNObservations. firstNObservations lacks description in both, so slight gap.

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?

Clear verb+resource: 'Query OECD data via SDMX'. Distinguishes from sibling tools like oecd_dataflows (list dataflows) and oecd_data_structure (get structure) by focusing on data retrieval.

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 specific usage advice: bound with startPeriod+endPeriod or cap with lastNObservations for large series. Does not explicitly state when not to use or compare to alternatives, but context is clear.

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