preflight_briefing

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

Provides a detailed list of checks performed (airspace class, UASFM ceiling, TFRs, NOTAMs, SUAs, etc.) and explicitly states the tool is read-only and does not modify the mission. No annotations exist, so description carries full burden and meets it well.

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?

Concise but comprehensive front-loaded summary followed by detail list. No wasted words. Each sentence adds value.

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 single parameter and no output schema, description sufficiently explains what the tool does, what it checks, and its side effects. Agent can confidently invoke it.

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?

Input schema describes mission_id as 'The UUID of the mission to brief' which is clear. Description adds context that the mission must exist and have waypoints, but doesn't specify the format of UUID. With 100% schema coverage, baseline is 3; description adds slight extra 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?

Clearly states it generates a comprehensive pre-flight briefing for a saved mission, combining waypoints with live airspace data to produce a GO/CAUTION/NO-GO recommendation. Distinguishes from siblings like check_airspace or check_live_traffic by specifying it integrates multiple data sources for a final recommendation.

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?

Explicitly states the mission must exist and have waypoints, and instructs to use list_missions to find mission IDs. Implicitly distinguishes from sibling tools that check individual airspace components by emphasizing the holistic briefing.

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