get_bookings_bookingid

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. With no output schema, the 'What You Get' section meaningfully discloses the return payload (status, guest info, pricing breakdown, cancellation policy, hotel confirmation code). No mention of auth requirements or behavior on an invalid/missing booking ID.

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 and well-sectioned, but padded: the overview already says it returns 'status, guest details, pricing, and cancellation policies,' which the 'What You Get' bullets then restate in six lines. For a single-ID getter, the markdown is longer than the task warrants.

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-by-ID tool with full annotation coverage, the definition covers purpose, contexts, and response contents adequately, and no output schema means return values do not need separate treatment. It omits error/not-found behavior, which 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 description coverage is 100%, so the baseline is 3. The description adds only that bookingId goes in the URL path; it does not clarify the timeout parameter or the ID format. Note the schema's own bookingId description says 'booking you would like to update,' which conflicts with this read operation, but the description correctly frames it as a lookup.

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 states a specific verb and resource: 'Get complete details for a specific booking by its booking ID.' That distinguishes it in kind from list/search siblings like get_bookings and searchBookings, though it never explicitly names an alternative. Clear and specific, but no direct sibling differentiation.

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 four concrete contexts (details page, status checks, confirmation lookup, support queries), which is solid situational guidance. It stops short of naming when NOT to use it or pointing to the list/search siblings for broader queries.

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