Search available indicators and datasets

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

Annotations already indicate readOnlyHint and other properties. The description adds useful behavioral details: it returns indicator keys with units and source notes, and can discover additional DBnomics datasets, providing 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 two sentences, efficiently covering purpose, examples, and output usage without unnecessary 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?

With one parameter and no output schema, the description sufficiently explains what the tool does and what it returns (keys, units, notes), linking to siblings. Minor area: could mention if there are limits or pagination, but not required.

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%, but the description enhances understanding by giving concrete examples ('inflation', 'debt') and mentioning additional dataset discovery, adding value beyond the schema's brief free-text description.

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 searches StatCite's curated indicator registry by topic, specifies the sources (World Bank, IMF, DBnomics), and explains it returns keys for use with siblings like get_indicator and verify_stat, distinguishing it from other tools.

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 example topics ('inflation', 'debt', etc.) and implies use when needing to discover indicator keys. It links to sibling tools but does not explicitly state when not to use or compare with the sibling 'search' tool.

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