query_worldbank

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

No annotations are provided, so the description carries the burden. It discloses the output behavior ('Output is written to file_path as CSV'), which is a side effect. However, it does not mention whether the tool is read-only in other aspects, any network usage, or potential errors. Partial transparency is present.

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, concise sentence with no redundant words. It efficiently conveys the purpose and key output detail.

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 simplicity of the tool (5 required parameters, no output schema), the description is fairly complete. It explains that output is written to a CSV file, which is essential. However, it does not clarify the return value (e.g., success indicator) or error handling, but these are minor gaps for such a tool.

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 schema descriptions cover 100% of parameters with examples for country and indicator. The tool description itself does not add additional meaning beyond the schema, so it aligns with the baseline of 3.

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 macroeconomic indicators', specifying both the verb (query) and the resource (World Bank). This distinguishes it from sibling tools that target other sources like arXiv, bonds, stocks, etc.

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?

No explicit guidance on when to use this tool over alternatives. The name and description imply use for World Bank data, but the description does not directly contrast with siblings or provide conditions for selection.

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