Check drone weather

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

Annotations already mark it read-only and open-world; the description adds that it returns an hourly advisory rating (good/caution/poor), names the data source, and states the default time window. This goes beyond the structured hints without contradicting them.

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?

Three sentences front-load the core data and rating, then give input instructions and defaults. No filler or repetition of schema details.

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 six parameters and no output schema, the description covers input selection, default behavior, and what the report contains (weather variables plus categorical rating). It doesn't state units or JSON shape, but the format parameter and schema fill most of the remaining 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?

All six parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds meaningful aggregation by telling the agent to provide 'a place or lat/lon' and that the date defaults to the next few hours, clarifying the implicit location requirement not captured by optional fields.

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 opens with a specific outcome ('Drone-relevant weather forecast for a UK point') and enumerates the exact variables and the flyability rating. This clearly separates it from sibling check_* tools focused on NOTAMs, terrain, airspace, or rules.

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?

It gives actionable invocation guidance: supply a place or lat/lon and optionally a date or date-time, with a default of the next few hours. It does not explicitly name alternatives such as preflight_briefing for a full briefing, but the weather-specific context makes the intended use unmistakable.

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