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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe read operation. The description adds value by specifying the returned content (line items, status history, participants), but does not disclose additional behavioral traits like rate limits or prerequisites. Since annotations cover the safety profile, a score of 3 is appropriate.

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?

The description is a single, front-loaded sentence of 12 words that efficiently communicates the tool's purpose and scope. Every word contributes to clarity, and there is no extraneous information.

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 retrieval tool with a single parameter and an existing output schema, the description provides sufficient context. It states what the tool returns (full details including line items, status history, participants), which is complete for appropriate use. The presence of the output schema reduces the need to describe return values.

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?

The input schema has 100% description coverage for the single parameter bookingId, with a schema description of 'The booking ID'. The tool description does not add further semantic meaning or usage hints for the parameter, so 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?

The description clearly states the action 'Get full booking details' and specifies included components (line items, status history, participants). This distinguishes it from sibling tools like get_booking_settings or get_booking_stats, as it focuses on comprehensive detail retrieval for a specific booking.

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 description implies usage when full booking details are needed, but it does not explicitly state when to prefer this over alternatives like list_bookings or get_booking_settings. No exclusions or alternative mentions are provided, making it adequate but not exemplary.

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