list_popular_indicators

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

No annotations are provided, so the description carries full burden. It effectively discloses behavioral traits: it's a read-only discovery tool (implied by 'Get' and 'curated list'), returns exactly 38 indicators with specific fields (codes, names, descriptions, categories), and provides the complete category breakdown. However, it doesn't mention potential limitations like rate limits or authentication requirements.

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?

Well-structured and appropriately sized. The description is front-loaded with the core purpose, followed by usage context, detailed category breakdown, return format, and clear next steps. Every sentence adds value with zero waste.

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 has 0 parameters, 100% schema coverage, and an output schema exists, the description provides excellent completeness. It explains the tool's purpose, when to use it, what it returns (including the exact count of 38 indicators and their structure), and how to proceed with sibling tools.

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?

The tool has 0 parameters with 100% schema description coverage, so baseline is 4. The description appropriately explains this is a parameterless tool for browsing curated content, which adds useful semantic context beyond the empty schema.

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 purpose: 'Get a curated list of popular World Bank indicators' with specific resource ('World Bank indicators') and verb ('Get'). It distinguishes from sibling tools like search_datasets_tool by emphasizing this is for discovery without searching, not for retrieving actual data.

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?

Explicit guidance is provided: 'Perfect for getting started or exploring what data is available' and 'Browse the list, pick an indicator code, then use search_datasets to find the exact database ID before retrieving data.' This clearly states when to use this tool versus alternatives like search_datasets_tool and retrieve_data_tool.

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