AviationHS charter quotes

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

Beyond the readOnlyHint annotation, the description discloses that the tool returns a reason rather than a simple boolean, and that the typical result is 'yes but with a payload penalty.' It also adds reliability caveats ('Indicative broker estimate', 'Not an offer of air transportation'), which an agent should know before relying on the result.

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 purpose and output behavior, followed by necessary caveats. The legal/broker disclaimers are somewhat verbose but are relevant to the tool's advisory nature; each sentence contributes meaningful context without obvious 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?

Given there is no output schema, the description adequately explains what the tool returns (a reason, not just a boolean) and the common shape of that reason. It also conveys the tool's advisory scope and limitations, which is important for a broker-related feasibility check. Minor gaps like error behavior or exact output structure are not critical for invocation.

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 both parameters documented in the input schema. The description adds context about what the tool evaluates (elevation, wingspan, weight) but does not add new detail about the format or syntax of the icao or aircraft parameters beyond what the schema already provides.

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 states a specific predicate: determines whether one aircraft can use one airfield, with explicit evaluation criteria (elevation, published wingspan, weight limits). This clearly distinguishes it from siblings like estimate_flight_time, get_quote, list_aircraft, and search_airports.

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 implies use as a planning aid and explicitly excludes it as a final authority ('operating carrier and its pilot in command decide'). However, it does not mention when to choose this tool over sibling tools or name alternatives, so usage guidance remains somewhat implicit.

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

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

The description discloses the exact computation method: great-circle distance with standard routing allowance, divided by published cruise, plus ground time, and a fuel-stop determination. It also explains that the result is an indicative broker estimate and that AviationHS is not a direct air carrier. This goes well beyond the readOnlyHint annotation and provides meaningful operational context.

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 compact and front-loaded with the core calculation and output. Each sentence earns its place: the formula, the indicative nature, and the regulatory disclaimer. The legal sentence is relevant because it frames how the result should be presented.

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?

There is no output schema, so the description carries the burden of explaining what the tool returns. It mentions the fuel-stop flag and the inputs to the calculation, but it does not specify the output format or units, nor does it clarify accepted input formats for from/to/aircraft. This is adequate for a simple estimator but leaves some ambiguity for an agent.

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 baseline of 3 applies. The tool description does not add material parameter-level guidance beyond what the schema already says: it does not explain what values from/to expect or how aircraft should be specified. The formula context is useful but does not clarify parameter formats.

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 conveys that the tool calculates an indicative flight time using great-circle distance, routing allowance, cruise speed, and ground time, and that it also indicates whether a fuel stop is needed. It does not use an explicit 'estimates flight time' verb phrase, and it does not distinguish itself by name from siblings, though the legal disclaimer separates it from quote/offer tools.

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 implies this is an indicative planning estimate rather than a binding quote or offer, which hints at when to use it. However, it does not explicitly state when to use this tool instead of siblings like get_quote or check_runway, nor does it provide exclusions.

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

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.

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: the data is 'indicative,' the entity is a broker under 14 CFR Part 295, and the listing is not an offer of transportation until a carrier confirms in writing. This goes beyond the annotation without contradicting it.

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 concise and front-loaded with the fleet attributes, followed by necessary legal caveats. The only minor redundancy is the repeated 'indicative' and slightly drawn-out broker disclaimer, but every clause contributes useful context.

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?

For a read-only catalog with no required parameters and no output schema, the description adequately names the expected output fields and important legal limitations. It does not describe return format or filtering behavior, but the input schema covers filters and no output schema exists to detail.

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% and all six parameters have clear descriptions, so the schema fully carries the parameter documentation. The description adds no parameter-specific meaning, but none is needed at this coverage level.

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 names the resource ('reference fleet') and enumerates the data fields the tool exposes: range, cruise, wingspan, balanced field length, and indicative hourly rate. It lacks an explicit verb like 'Lists' or 'Returns,' but the meaning is clear and the tool is readily distinguishable from its airport/runway/quote siblings.

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 provides no explicit guidance on when to use this tool versus alternatives such as check_runway, estimate_flight_time, or get_quote. The legal and broker-status caveats are useful context but do not help an agent decide when to invoke this tool.

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

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

With readOnlyHint/openWorldHint already in annotations, the description adds value by disclosing the reference-set size (847), the 'Indicative broker estimate' nature, and the Part 295 broker/not-a-carrier legal context. No contradiction with annotations.

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 core purpose is front-loaded in the first sentence, followed by necessary scope and disclaimer context. A few boilerplate legal caveats take space, but every sentence provides some selection/use-relevant context.

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?

The description covers the tool's purpose, dataset scope, estimation nature, and legal status, while the schema covers all parameters. With no output schema, it would benefit from a bit more on return shape, but the description is otherwise sufficient for correct invocation.

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 are already described in the schema (100% coverage), so the baseline applies. The description clarifies 'field' semantics and the runway filter, but adds little beyond the schema for individual parameters.

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?

States a specific verb ('Find') and resource ('US airport'), with explicit search keys (name, city, ICAO, IATA) and an optional mode (nearby fields filtered by runway length). The scope ('business jet can actually use') also differentiates it from the sibling list_aircraft and check_runway tools.

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 the intended use clear: locate US airports or nearby usable fields by identifier/name or runway capability. It does not explicitly name alternatives or exclusion conditions, but the 'find vs. check/quote/list' context is strong enough to guide selection.

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