oecd_compare

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

No annotations are provided, so the description must carry the full transparency burden. It discloses one behavioral detail: 'period... if empty, uses latest values per country.' However, it fails to mention return format, pagination, or any limitations. The default behavior for period is helpful but insufficient overall.

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 extremely concise: one sentence for purpose and one line for parameter hints. It is front-loaded and contains no fluff, making it easy to parse quickly.

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?

The tool has 3 parameters, 2 required, and an output schema. The description covers only two parameters and omits the essential indicator parameter. It also does not mention any caveats or limitations beyond the period default. Given the simplicity of the tool, the description is incomplete.

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 0%, so the description must compensate. It explains the countries parameter format (comma-separated) and the period default behavior, but it does not explain the indicator parameter at all, even though it is required. This is a significant 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?

The description clearly states the tool's core function: 'Compares the same indicator across multiple countries at once.' This is a specific verb (compare) with a specific resource (same indicator) and scope (multiple countries), which distinguishes it from sibling tools like oecd_trend or oecd_rank.

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 provides no guidance on when to use this tool versus alternatives. It only gives parameter formatting examples and does not mention any exclusions, prerequisites, or alternative tools.

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