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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is already met. The description adds real behavioral context beyond that: the review call refreshes the fare before handoff, the total originates from this call, and the review page always precedes the Paytm handoff. It stops short of describing latency or failure modes, so 4 rather than 5.

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?

Leads with what the page shows, then usage, then parameters — well front-loaded and dense with non-redundant facts. It is long, and the handoff-ordering point ('review page comes before any handoff') overlaps with the earlier 'refreshes the fare before handoff' sentence, costing it a point.

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 7-param tool with an output schema and full annotation coverage, the description supplies everything else an agent needs: workflow position, token semantics, the recommended-fare fallback, and round-trip handling. Return values can be left to the output schema.

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?

Despite 100% schema coverage, the description adds meaning the schema does not: offer_token may be the long signed token or the short offerRef and "a short value is valid, not an internal id", it must be matched exactly, and omitting price makes the tool fetch the recommended best-value fare. It also explains price/fare_name are used verbatim and that Saver vs Flexi map to different Paytm ids.

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?

Specific verb+resource: shows the flight details/review page for a selected fare, and enumerates what it renders (itinerary, fare breakdown, refundability, Book link). It explicitly positions itself relative to siblings (after get_fare_family, before Paytm handoff), so an agent can distinguish it from get_flight_details and get_fare_family without opening any 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?

Names the exact triggering utterances ("continue, review, see flight details for a chosen fare, or book after picking a fare") and the fare-family Continue CTA that lands here. It also states what is NOT needed (no new search or fare-family call to settle on a fare), giving both when-to-use and when-not.

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