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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuine extra context by disclosing that results are estimates, that it relies on cwsi.net's calculator plus published rules, and that it is "Unofficial" – all useful for calibrating trust in the output.

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?

A single compact sentence leads with the core purpose and tucks the provenance and "Unofficial" caveat into a short trailing clause. Nothing is wasted, though the parenthetical is slightly dense.

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?

With an output schema present, the description need not explain return values, and annotations handle the safety profile. The description covers purpose, estimation caveat, provenance, and scope, which is sufficient for a low-risk, single-required-parameter calculator.

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 each enum value (card, fare, status) is already fully documented in the schema. The description adds no fare/status/card semantics beyond what the schema provides, so the baseline of 3 applies.

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 pairs a specific verb ("Estimate") with a specific resource ("what a Breeze Airways ticket earns") and even names the sub-outputs (miles or points, status credit). The Breeze Airways name naturally separates it from the many sibling airline calculators, though it never explicitly frames itself as the Breeze-specific alternative.

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?

Usage is implied by the airline scope and the earnings context, but there is no explicit when-to-use guidance, no prerequisites, and no pointer to a sibling or alternative. Nothing tells the agent what a caller must already know (fare/bundle data) before invoking it.

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