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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds real behavioral detail beyond them: which status values exist and what extra payload accompanies each (deposit link once payable, driver's note on decline), plus the identity pair required to read a record.

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 sentences, front-loaded with the outcome enumeration and ending with the required inputs. No filler and nothing repeated across sentences.

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, the description correctly carries the return-value burden by describing each state and its associated data. Minor gaps remain around what happens on a ref/e-mail mismatch (not found vs. forbidden) and whether the deposit link expires.

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 67%; ref already documents its CP-XXX-XXX shape and lang documents the 'ar: Arabic notes, data in English' behavior. The description's contribution is the constraint that the e-mail must be the one belonging to the request, which the email field itself does not say — useful, but the lang parameter stays unexplained in the description.

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 uses a precise verb-and-resource framing ('What became of a booking request') and enumerates the possible states, so the agent knows exactly what is retrieved. It is clearly distinct from the write-side sibling request_booking, though it never names a sibling explicitly.

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?

It states the prerequisites ('Needs the reference and the e-mail address of the request'), which effectively conveys that this is a lookup of an existing booking rather than a search or a new request. It gives no explicit when-not guidance or named alternatives (e.g. request_booking, quote).

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