worldbank_get_country_ranking

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

There are no annotations, so the description must carry the behavioral burden. It does disclose sorting order ('sorted by value descending'), the year default behavior ('uses most recent available'), and optional filtering by income group. This is solid but does not address error conditions, missing data handling, or whether the tool is read-only.

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 compact and well-structured: a one-sentence purpose followed by Args and Returns sections. No filler or redundant wording, and the core purpose is front-loaded.

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 low-complexity tool with an output schema, the description covers the key execution context: parameters, default behavior, and return ordering. Minor gaps like invalid indicator codes or rate limits would be nice but are not essential to successful invocation.

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 0%, so the description must compensate. It provides meaningful explanations for all three parameters: indicator as a World Bank code, year with default behavior, and income_group as an optional filter. This fully covers the semantic gap left by the 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 opens with a specific verb and resource: 'Rank countries by a World Bank indicator value.' This clearly distinguishes the tool from siblings like worldbank_get_data (raw data retrieval) and worldbank_search_indicators (indicator discovery).

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 when to use the tool—when you want a ranking rather than raw data—but it never explicitly states alternates or exclusions. No mention of 'use worldbank_get_data for raw values' or conditions under which this tool would be inappropriate.

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