weather_uae_icao

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

No annotations are provided, so the description carries the burden. It states the tool fetches current observation and optional forecast but does not mention data freshness, error handling, or units. The existence of an output schema mitigates some need for return value details.

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?

A single, clear sentence with no wasted words. Front-loaded with the action and result.

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 existence of an output schema and the simplicity of the tool (two parameters, one required), the description is complete enough for an agent to select and invoke it correctly. It could mention that only UAE airports are supported, but the name and parameter description make that clear.

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 covers both parameters with 100% completeness. The description adds context that the tool gets METAR and optionally TAF, reinforcing the purpose but not adding new meaning beyond the 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?

The description uses specific verb 'Get' and identifies the resource as 'METAR (current weather observation) and optional TAF (forecast)' for a UAE airport. It distinguishes from sibling tools like weather_by_coords and weather_uae_all by focusing on ICAO codes.

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 implies usage for UAE airport weather but does not explicitly state when to use this tool versus alternatives like uae_weather or weather_uae_all. No exclusions or context are provided.

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