preflight_briefing

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

With no annotations provided, the description carries full burden and clearly states the tool is read-only and does not modify the mission. It also outlines all the data sources it checks, providing full behavioral transparency.

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?

The description is well-structured with a clear main purpose, followed by a bulleted list of checks. It is comprehensive but not verbose, earning its place. Slight improvement could be front-loading the usage tip earlier.

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 a complex tool performing many checks, the description is quite complete, covering prerequisites, behavior, and output. No output schema exists, but it mentions returning issues, recommendations, and a disclaimer.

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?

The schema covers 100% of the single parameter, providing a description of 'mission_id'. The description adds meaning by specifying that the mission must exist and have waypoints, enriching the semantic understanding 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 clearly states the tool generates a comprehensive pre-flight briefing, combining mission waypoints with live airspace data to produce a GO/CAUTION/NO-GO recommendation. It lists all the checks it performs, distinguishing it from siblings like check_airspace and check_live_traffic.

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 explicitly says the mission must exist and have waypoints, and advises using list_missions to find mission IDs. It implies when to use (for saved missions with waypoints) and clarifies it is read-only, but does not explicitly mention alternatives or when not to use.

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