rank_countries

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the core action. It does not indicate ranking direction (ascending/descending), tie handling, missing data behavior, or whether it returns only top N despite the top_n parameter. No behavioral traits are disclosed.

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?

A concise one-sentence description that wastes no words. It is appropriately sized for a simple tool while still including the core action and object.

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 fails to mention key behavioral aspects like the top_n limit or region filtering, which are crucial for a ranking tool. Even with schema coverage, the overall context is incomplete for a tool with 3 parameters and an output schema.

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 has 100% coverage of all parameters (indicator, top_n, region) with descriptions, so baseline 3 applies. The description adds no extra meaning beyond the schema; 'indicator value' merely mirrors the indicator parameter.

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 'Rank countries by indicator value' uses a specific verb (rank) and resource (countries), clearly distinguishing it from siblings like compare_countries or get_data. It conveys a distinct operation on countries based on indicator 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?

No guidance is provided on when to use this tool versus alternatives like compare_countries or analyze_trend. The description does not mention any context, exclusions, or alternatives.

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