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

Annotations already cover readOnly, idempotent and non-destructive semantics, so the bar is lower; the description nonetheless adds real value by enumerating the returnable statuses (including the non-obvious 'accepted = confirmed, including instant bookings') and by disclosing that no guest personal data is returned. It stops short of noting anything about lookup failure behavior for unknown IDs.

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?

Two short sentences plus a lead-in, front-loaded with the read-only nature and the key noun, then the status enumeration. Every clause carries information; nothing is padded.

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?

There is no output schema, so the description correctly carries the return-value burden by listing statuses and the fields returned (dates, room, price) plus a privacy caveat. For a single-parameter read tool this is complete enough to call correctly.

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?

With one parameter and 0% schema description coverage, the description compensates by naming the parameter's purpose ('by its booking_id') and supplying a concrete format example (BKD-AB12CD3), which the schema's maxLength alone does not convey. It does not state whether the ID is case-sensitive or how to obtain it.

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 (read, retrieve status) and resource (Bookd booking) with an ID format example, and enumerates the exact status values returned. It is clearly distinguishable from siblings like cancel_booking or request_booking, which mutate state.

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 'Read-only' opener and the status lookup framing imply the use case (checking an existing booking's state), but the description never states when to prefer this over siblings or what preconditions apply (e.g. that the booking must already exist). Adequate but with an explicit-guidance gap.

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