World Bank indicator time series

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

Annotations declare the tool as read-only, idempotent, and non-destructive, so the burden is low. The description adds context about parameter values (e.g., country ISO codes, 'all', 'WLD') and date range format, but does not mention rate limits or pagination behavior beyond the schema.

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, front-loading the purpose and immediately providing concrete examples. Every sentence is informative and necessary with no redundancy.

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's simplicity (4 params, no output schema), the description covers the essential information: purpose, parameter examples, and format hints. It does not explain the return structure, but for a time series retrieval, the agent can infer from the indicator context.

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 75%, and the description adds significant value by providing example indicator codes (NY.GDP.MKTP.CD, etc.) and explaining country parameter options (ISO, 'all', 'WLD'), which go beyond the schema's terse descriptions.

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 'Time series for a World Bank indicator and country' and provides specific examples of indicators and country codes, distinguishing it from sibling tools that return metadata, country info, or search results.

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 use for retrieving time series data but does not explicitly state when to use this tool versus alternatives like worldbank_indicator_metadata or worldbank_search_indicators. No exclusions or alternative suggestions are provided.

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