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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so the safety profile is covered. The description adds real value by disclosing the authorization behavior: the server only returns or changes a booking when the id and email match, which is exactly the kind of context annotations don't carry. The word 'changes' is slightly loose against readOnlyHint but the sentence is about the auth precondition, not a write claim.

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?

Two sentences, front-loaded with what the call returns and then the preconditions. No filler; every clause carries information an agent needs.

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 lookup with full annotation coverage and no output schema, the description is nearly complete: it names the return fields and the auth requirement. It stops short of return format or pagination details, but those are not essential 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?

Schema description coverage is 100%, so the schema already documents all three parameters including the matching check. The description reinforces the bookingId/email pairing but adds no new syntax or format meaning, so the baseline 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?

States a specific verb (look up) and resource (confirmed flight booking) and enumerates the returned contents: status, passengers, flights, booking references, fare rules and price. This lets an agent distinguish it from the generic get_bookings_bookingid and from hotel/experience booking siblings 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?

It gives a clear precondition for use — the bookingId and the email used to book must both be supplied and match — which is the key context for calling it correctly. It does not explicitly name alternative tools or when-not-to-use cases, but the scope ('confirmed flight booking') implicitly separates it from the hotel/experience booking siblings.

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