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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is covered. With no output schema, the description carries real weight by disclosing the response contents (refund schedule, verification link, arrival-detail timing), which is genuinely useful behavioral context beyond the annotations.

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?

A single dense fragment listing return fields followed by the endpoint mapping — front-loaded with the payload contents an agent cares about, with no filler. It reads as a noun list rather than a sentence, but nothing is wasted.

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 one-parameter read tool, the return-content listing compensates for the missing output schema and the annotations cover safety. What is missing is any usage context (when this beats get_quote/get_property) and error behavior for an invalid or unknown booking_id.

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?

One required parameter with 0% schema description coverage, so the schema alone does not explain booking_id's origin or format. The endpoint mapping implies booking_id is the booking identifier, partially compensating, but no format or source guidance is given.

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 names the resource (booking) and enumerates the specific fields returned — status, amounts, refund schedule, guest ID verification link, arrival-details timing — and anchors it to GET /v1/bookings/{id}. An agent can tell this is the booking-detail reader, though it never contrasts itself with siblings like get_quote or get_property.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The only routing hint is the REST endpoint mapping, which an agent must infer means 'call this when you already have a booking_id'.

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