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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description goes further by disclosing that the response contains private intake details (a sensitivity warning) and that the tool deliberately does NOT redispatch uncertain operations or reconstruct manage credentials. That is real behavioral context beyond the structured fields, though it omits pagination/limits on the receipts.

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?

Three short sentences, front-loaded with what is returned, followed by sensitivity and negative-scope caveats. No filler, though the phrasing is dense/jargon-heavy ('bounded operation receipts', 'manage credential') for an agent with no surrounding context.

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?

No output schema exists, so the description should carry return-value meaning; it names two payloads (booking, operation receipts) and flags private intake details, but does not characterize the receipts shape, count limits, or failure/absent states. Combined with undocumented parameter format, the definition is usable but incomplete.

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?

Only one parameter exists and schema coverage is 0%, so the schema gives no help. The description partially compensates by implying ownership scoping ('owned booking') and that a specific booking is targeted, but it never states that booking_id is a UUID or where the identifier comes from. Adequate-but-gapped rather than rich.

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+resource ('Read one owned booking') plus a secondary payload ('bounded operation receipts for recovery'), which is enough to distinguish it from list_bookings, cancel_booking and reschedule_booking by scope. It never names a sibling, so differentiation is inferred from 'one ... booking' rather than stated.

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 phrase 'for recovery' implies the context in which this tool is called, and the closing sentence rules out two tempting misuse paths (redispatched operations, reconstructed manage credentials). But there is no explicit 'use this instead of X when Y' routing against list_bookings or get_* siblings, so guidance stays implicit.

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