İstanbul hava kalitesi: istasyon bazında AQI, PM10, SO2, O3, NO2, CO

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

Annotations already provide readOnlyHint and openWorldHint, but the description adds valuable behavioral context beyond that: it mentions the data source (web service), specifies the conditional behavior on the parameter, and states the units (µg/m³, CO mg/m³). This is meaningful disclosure beyond the structured fields, with no contradiction.

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 bilingual and moderately detailed, but not excessively long. It front-loads the core information (what data it returns) and each sentence adds substantive detail (parameter behavior, units). The bilingual repetition is slightly redundant but does not undermine clarity, so it earns a 4 rather than a 5.

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 the tool's low complexity (one optional parameter) and the existence of an output schema, the description provides sufficient context: it explains the parameter modes, data source, and units. No critical information is missing for an agent to call the tool correctly, so a 4 is appropriate.

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 description coverage is 100% for the single optional parameter `istasyon`, which already says it accepts a station name or fragment. The description enriches this by clarifying the two possible response modes (all stations vs. a 24-hour series for one station), which is not evident from the schema alone. This adds real value.

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 and specifically states that the tool provides the latest air-quality readings from Istanbul's municipal monitoring stations, enumerating the pollutants (AQI, PM10, SO2, O3, NO2, CO) and noting the source (İBB Açık Veri Portalı). It establishes a distinct purpose that is unambiguously different from sibling tools like weather or earthquake services, even without explicit contrast.

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 gives clear context on how to use the tool, explaining that omitting the `istasyon` parameter returns all stations and providing it returns a 24-hour series for that station. However, it does not explicitly mention when to prefer this tool over alternatives or state any exclusion criteria, 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.