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

Annotations already declare read-only, non-destructive, and open-world, so the safety profile is covered. The description adds real behavioral value beyond that: it is a live provider round-trip ('Real-time price check'), warns that prices can drift ('avoid price discrepancies'), and documents the `changes` payload replacing deprecated scalar currency/prices fields.

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?

Front-loaded with an Overview, but the body is padded and repetitive: 'Real-time price check', 'Fare rules', and baggage/price confirmation information are restated across Overview, What You Get, and Key Features. The markdown structure helps navigation but several sections earn less than their length.

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 no output schema, the description legitimately carries the return-shape burden and does so in detail (pricing breakdown, journey pricing, fare family, baggage, booking terms). It still omits error handling, auth/permission needs, and rate limits for a live provider call.

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?

Only one parameter with 100% schema coverage; the schema already documents offerId. The description adds the source endpoint ('/flights/rates') and the downstream use ('populate a booking summary page'), which is marginally useful, but the schema does the heavy lifting.

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 Overview states a specific verb and resource ('Confirm a flight offer is still available and retrieve the latest pricing') and situates it in the booking pipeline ('before proceeding to booking'). Combined with the sibling list, an agent can distinguish this from post_flights_rates (search) and post_flights_prebooks (booking) without opening a schema.

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 'When to Use' section gives three concrete situations (pre-booking validation, price confirmation, fare rule retrieval) plus a 'Quick Start' naming the source endpoint. It lacks explicit when-not-to-use or named alternatives, which caps it below a 5.

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