search_indicators

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

No annotations are provided, so the description carries the full burden. It only states the basic search functionality without disclosing behavioral traits such as pagination, rate limits, error handling, or whether results are limited. The implied read-only nature of 'search' is not explicitly confirmed.

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 a single, efficient sentence with 12 words. It is front-loaded with the verb and resource. However, it could include slightly more detail without becoming verbose.

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?

For a simple tool with 2 parameters and no output schema or annotations, the description is minimally adequate. It tells the basic purpose and gives examples, but lacks details about the return format, result limits, or how it differs from sibling tools like list_categories_detailed.

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 both parameters having descriptions. The description adds no additional meaning beyond the schema; it rephrases the search parameter as 'by keyword' but does not provide syntax, format, or examples for the parameters.

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 verb-resource combination 'Search for specific economic or social indicators' and provides concrete keyword examples ('inflation', 'unemployment', 'GDP'). This distinguishes it from sibling tools like query_data (which queries data values) and search_dataflows (which searches for dataflows).

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 implies using this tool when searching for indicators by keyword, but does not explicitly state when to use it versus alternatives or provide any exclusions. The examples help, but there is no guidance on when not to use this tool.

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