air_quality_hebei

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so safety is covered. The description adds the data source URL, the 6-day forecast horizon, and the pandas.DataFrame return type, which is useful context, but it does not explain freshness, update cadence, or coverage limits.

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 content is compact but structured as raw source docstring fragments (URL, ':return:', ':rtype:') in mixed Chinese/English, and the return-type metadata is not front-loaded. It reads as pasted documentation rather than a crafted description.

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 no-argument read-only forecast tool with no output schema, the description conveys scope (6 days, Hebei) and return type, which is roughly adequate. The unresolved city-parameter mismatch is the main completeness gap.

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 declares zero parameters, yet the description documents a 'city' argument (city="" returns all regions; city="唐山市" returns Tangshan). That meaning is helpful in isolation but contradicts the empty input schema, leaving the agent unsure whether city can actually be passed.

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 a specific verb+resource: Hebei Province air quality forecast for the next 6 days, with the issuing system and URL. It is clearly distinguishable in subject matter from the finance/macro siblings, though it does not explicitly name any sibling it maps against.

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 when-to-use, when-not-to-use, or alternative guidance is given. The only usage hint is the city-filter behavior, and that is presented as part of the return note rather than as routing guidance.

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