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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that—no indication of what status values may be returned, whether the status is real-time or cached, or what happens for a cancelled/unknown booking.

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, front-loaded sentence with no filler. It is efficient but so short that the brevity comes at the cost of the missing detail noted elsewhere.

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 should describe the return payload (status fields, possible states, error behavior for unknown IDs) and it says nothing. For a status-lookup tool the return semantics are the core value, and they are entirely absent.

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 0%, so the description must compensate and it does not: booking_id has no documented format, source, or example. 'Existing booking' only hints that the ID must reference a real booking, leaving the agent to guess the identifier's shape.

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 ('check') and resource ('status of an existing booking'), which is clear enough to distinguish it from mutation siblings like cancel_booking and create_booking. It is less clearly differentiated from read siblings such as get_booking_session and get_trip_details, which the description never mentions.

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?

No guidance on when to use this versus get_booking_session, get_trip_details, or search_availability, all of which likely return overlapping booking information. The phrase 'existing booking' only weakly implies a prerequisite (the booking must already exist) and gives no exclusions.

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