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

With no annotations, the description carries the full burden and delivers: discloses exact return fields (business, local date/time with timezone, party size, service, status enum with all values), the payment_url conditional, the privacy guarantee ('never returns the guest's name, email or phone'), and security behavior ('wrong or missing token is refused without revealing whether the booking exists'). This is unusually rich disclosure.

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-loads the purpose, then credentials, then return shape, then security behavior. Dense but every sentence carries information. The status enumeration is slightly list-like but earns its place by telling the agent what states to expect.

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, no annotations, two required parameters — the description compensates by enumerating expected return values, statuses, conditional fields, and failure behavior. An agent has everything needed to call and interpret this tool.

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%, so both parameters are already documented. The description reinforces provenance (create_booking return / manage link, token from ?token=) but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 ('Look up one existing booking') with explicit scope ('so the guest can confirm when and where it is'), clearly distinguishing read-only lookup from sibling mutations like create_booking and cancel_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?

Names create_booking as the source of the required credentials and explains where guests find them (confirmation email / manage link). Doesn't explicitly say when not to use this versus search or fetch, but the single-booking scope is clear from the text.

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