uae_weather_forecast

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and an output schema exists, so the safety/format profile is covered structurally. The description adds 'no API key needed', which usefully signals no auth setup, but omits rate limits, forecast freshness, or error behavior.

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 front-loaded sentence with no wasted words. The parenthetical is efficient, though the description is arguably too terse to carry routing guidance.

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?

Output schema and rich annotations cover return values and safety, and the schema documents both params, so the description is only required to add routing context. It largely fails to do so, leaving no explicit differentiation from the several other weather tools.

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 coverage is 100%: city and days are both documented with defaults and the 1–16 clamping rule. The description adds no parameter detail beyond what the schema provides, so the baseline 3 applies.

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: a multi-day daily weather forecast for a UAE city. This is clear enough to separate it from a current-conditions tool, but it never explicitly names the sibling it differs from (e.g. uae_weather, weather_by_coords, weather_uae_icao), so an agent must infer the distinction.

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 phrase 'multi-day' implies when this tool is chosen over a current-conditions sibling, but no when-to-use, when-not, or alternative is stated. Usage is left to inference from the sibling list.

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