Get booking

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about the payload contents (times, status, booking page, form answers), but says nothing about permissions, error behavior for a missing/invalid ID, or the fields override's effect.

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 that names the resource first and then the returned content. Every clause carries information; there is no filler.

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 read-only lookup with no output schema, the description's enumeration of returned data adequately compensates for the missing output schema. Only minor gaps remain: no note on behavior when the booking is not found and no guidance on the optional fields override.

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 both bookingId and the fields override are documented in the schema itself; baseline 3 applies. The description adds no meaning beyond the schema - it doesn't explain what the 'fields' override does or why one would use it.

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 ('Get') and resource ('one booking') and enumerates what comes back: times, status, booking page, and the booker's form answers. It is clearly distinguishable from the list-oriented siblings (search_bookings, list_upcoming_bookings), though it never names them 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?

There is no explicit when-to-use/when-not statement in the description. Usage is only implied: fetching a single booking by ID versus the list/search siblings. The schema's bookingId note ('from search_bookings or list_upcoming_bookings') supplies the workflow hint, but that is structured data, not the description.

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