World Bank Open Data

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

Annotations declare readOnlyHint and idempotentHint, but the description adds that the tool is '完全免费，无需认证' (completely free, no authentication required), which is beyond annotations. This clarifies access requirements and cost, enhancing transparency.

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 concise: a short introductory sentence, clear parameter definitions with defaults, and a list of common indicators. No redundant information, and the structure is easy to parse.

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 description lacks details about the return format or data structure, which is not covered by an output schema. While it includes common indicators and defaults, an agent may need to know the shape of the response to use the tool effectively.

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?

All 4 parameters are described both in the schema and in the description. The description adds value by explaining that indicator can be a common name or WB code, countries are ISO3 codes with defaults, and provides a list of common indicators for reference.

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 '查询世界银行开放数据' (query World Bank open data) and specifies supported indicators (GDP, CPI, etc.) and global 200+ countries. It distinguishes itself from sibling tools like ext_world_bank_indicators and ext_world_bank_multi by focusing on data querying with parameters.

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 explains parameters and lists common indicators but does not provide explicit guidance on when to use this tool versus its siblings. Usage context is implied but not contrasted with alternatives.

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