查询空气质量

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

No annotations provided, so description partially compensates by noting no API key required and listing pollutants. However, it omits other behaviors like rate limits, data freshness, error handling, or return format.

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?

Two concise sentences in Chinese that front-load the main purpose. No filler or redundancy; every sentence adds useful information.

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 tool with no output schema, the description adequately states what is returned (AQI and specific pollutants) but lacks details on the response structure or data format, leaving some uncertainty.

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 covers 100% of the city parameter with description. The description adds value by specifying language support (Chinese/English) and providing examples (e.g., Beijing, Shanghai, Tokyo), going beyond basic 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?

Description clearly states the tool queries air quality index (AQI) for a city, listing major pollutants (PM2.5, PM10, etc.). It is specific and distinct from sibling tools (weather, forecast), making the purpose unambiguous.

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 on when to use this tool vs siblings (e.g., get_current_weather, get_forecast). It mentions support for Chinese/English names and no API key, but lacks explicit when/when-not context.

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