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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavior beyond that by disclosing the identity-verification requirement (email proves ownership), which is important for an agent to know before invoking.

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 tightly packed sentences: the first front-loads the action and enumerates key return fields, the second states the required inputs. No filler or repetition of the title.

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?

With no output schema present, the description helpfully lists what is returned (status, vehicle, office, dates, total) and confirms the required credentials. Annotations cover safety, and the schema covers all parameters, so the definition is nearly complete; only error/not-found behavior is left unstated.

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 100%, so all four parameters are already documented in the schema, and the description only restates the booking reference and email requirement. It adds no format or syntax details and omits company_id and language entirely, so it neither helps nor harms beyond the schema baseline.

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 and resource ('Look up a booking made through Bota') and enumerates the returned fields, so it is immediately distinguishable from mutating siblings like confirm_booking and cancel_booking. An agent knows exactly what operation this performs without reading the schema.

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?

Clearly establishes the prerequisites for use ('Needs the booking reference and the email it was made with'), which is the key gating condition for calling it. It does not explicitly say when to prefer a sibling tool (e.g., cancel_booking) instead, but the read-only lookup context is unambiguous.

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