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

Adds substantial context beyond the annotations: the exact auth mechanism (Firebase phone-OTP Bearer idToken) and the access-control rule that a booking is only returned when its phone matches the verified caller. It doesn't cover failure modes (403 vs 404, rate limits), so it falls short of a 5.

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 action and immediately followed by the precondition that governs it. 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?

Auth and ownership behavior are well covered, and no output schema exists so return values need not be described. However, the ambiguous optionality of email vs bookingId leaves an agent unsure how to actually invoke the call, which is the main remaining gap.

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% and neither the email nor bookingId parameter is explained in the description. Notably both parameters are optional (required: 0), and the description never clarifies whether lookup needs one, the other, or both — a gap the text should have closed.

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 ("Retrieve a booking") and scopes it to bookings the caller owns, which separates it cleanly from siblings like start_booking or quote_booking. An agent can identify the operation without opening 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?

The ownership/auth framing implies this is for fetching an existing booking rather than creating one, but the description never explicitly states when to prefer it over siblings such as start_booking or quote_booking. No when-not guidance is given.

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