get_flights_bookings_bookingid

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety profile is covered. The description adds return content details (itinerary, passenger manifest, pricing breakdown, provider reference) not found in annotations. No auth or rate-limit info, but for a read tool with rich annotations this is adequate.

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?

Markdown sections and bullet lists are structured but overly verbose for a single-parameter read. 'What You Get' and 'Key Features' repeat the same return content (full booking record, passenger details, provider reference), making several sentences redundant.

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 simple read tool with rich annotations and no output schema, the description covers purpose, usage contexts, and return values adequately. Missing edge cases like invalid booking ID handling, but that is a minor gap.

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% and bookingId is documented as 'the unique booking identifier'. The description adds that the ID is returned from POST /flights/bookings and should be placed in the URL path, providing useful provenance and location beyond the schema.

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 'retrieve' and resource 'complete details of a confirmed flight booking' using its unique booking ID. Distinguishes from sibling list tool get_flights_bookings and general get_bookings_bookingid by specifying 'flight booking'. An agent can easily tell what this tool does.

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?

Provides a 'When to Use' section with four concrete scenarios (confirmation page, management, itinerary display, status checks). However, it does not explicitly name alternatives or state when not to use this tool, so routing guidance is clear but incomplete.

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