rank_country_changes

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

Annotations already declare readOnlyHint=true, so the description adds unit and comparison details but doesn't disclose additional behavioral traits like pagination or data completeness. The description adds some value beyond annotations but is not extensive.

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, with the purpose front-loaded and unit details in a separate paragraph. No wasted words.

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 12 parameters with 0% schema coverage and an output schema, the description is insufficient to guide correct usage. It does not explain filtering parameters, ordering, or the meaning of the change units in relation to the output.

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 coverage is 0%, so the description must compensate. It explains metric units but leaves 11 other parameters unexplained. The parameter names like min_year_count and min_period_years are ambiguous without description.

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?

States specific verb 'rank' and resource 'countries by change', and explicitly differentiates from indicator_trend for unranked summaries. The purpose is clear and distinguishes from siblings, though 'change' could be more precise about the time range.

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?

Explicitly names alternative tool for unranked summaries, and provides unit conventions. Gives clear context for when to use this tool vs indicator_trend, and clarifies metric units.

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