air_quality_rank

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the source URL and return type (pandas.DataFrame), but does not disclose the structure of the returned ranking data or any error/limitation behavior. No contradiction with annotations.

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-organized, with a title, URL, and param/return sections. The URL adds useful provenance, though it could be omitted for brevity. Overall, every sentence serves a purpose.

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 single-parameter, read-only tool, the description covers the parameter semantics and return type adequately. It lacks a description of the returned columns or the fixed descending order, but the title and source URL provide sufficient context for basic use.

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%, but the description fully documents the sole parameter 'date' with four distinct format options and their meanings. This completely compensates for the lack of schema-level descriptions.

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 this is an AQI ranking for 168 cities from the Zhenqi Net (真气网-168 城市 AQI 排行榜). It specifies the data type returned (air quality ranking data) and the source URL, making it distinct from sibling air quality tools that focus on historical data or specific regions.

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 provides explicit context on how to use the date parameter with examples for current, daily, monthly, and yearly rankings. It does not, however, mention alternatives or when not to use this tool relative to other air quality functions, so it falls short of a 5.

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