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

The annotations only declare readOnlyHint=true and openWorldHint=false, so the description carries the burden of behavioral context. It adds substantial value: the estimate is indicative, AviationHS is a Part 295 broker rather than a direct air carrier, and the result is not an offer until an operating carrier confirms in writing. It also discloses what is included and why certain aircraft are excluded.

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 front-loaded with the core action and scope, then adds behavior, inclusions, and legal context in dense, purposeful sentences. Every sentence contributes meaningful information; there is no filler or redundancy.

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?

Despite lacking an output schema, the description explains the pricing scope, inclusion items, exclusion logic, legal status, and the indicative nature of the result. An agent has enough information to call the tool correctly and interpret the high-level response.

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 description coverage is 100%, so the schema already documents from, to, pax, and date. The description does not add much parameter-level detail, though 'either runway' and 'reference fleet' provide some context for interpreting from/to and aircraft selection. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 verb and resource: 'Price a trip' and then defines the exact scope—every aircraft in the reference fleet that carries the party, with runway-ineligible aircraft excluded and reasons given. This clearly distinguishes it from siblings like estimate_flight_time and check_runway.

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 makes its context clear: this is the tool for getting a full indicative charter quote including crew, landing, handling, daily minimum, and federal excise tax. It does not explicitly state when not to use it or name alternatives, so it misses the explicit when/when-not guidance of a 5.

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