validate_flight

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

Description declares read-only nature clearly. Annotations are missing, so description carries full burden. It discloses status values (PASS, CAUTION, FAIL) and that it checks multiple rules, but does not detail behavior of each check (e.g., time-based logic for civil twilight).

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, each adding value: purpose, specific checks, return status. No fluff. Front-loaded with primary action.

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 no annotations and no output schema, description covers purpose, checks, return status, and read-only nature. Missing details on pagination or response format, but acceptable for a validation tool with simple boolean-ish output.

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% with adequate descriptions for each parameter. Description adds context for altitude_ft (400ft AGL limit) and time (defaults to now), but does not go beyond what schema already provides for lat/lng. No contradiction.

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?

Description states specific verb ('validate'), resource ('a drone flight'), and scope ('under FAA Part 107 rules'). Clearly distinguishes from siblings like check_airspace and get_active_tfrs by listing specific checks (TFR, altitude, UASFM ceiling, civil twilight).

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?

Description implies usage before flight planning, but does not explicitly say when not to use or direct to alternatives. Siblings exist (check_airspace, get_active_tfrs) that might be more targeted, but no exclusion guidance.

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