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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered; the description's real contribution is disclosing the returned payload in detail, which matters because there is no output schema. It does not say what happens for a nonexistent or unauthorized booking id, leaving that behavior unstated.

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 a one-line summary of the returned record before the enumerated detail. Slight redundancy — 'price breakdown' and provider pay are named twice in quick succession — but 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?

With no output schema, the description does the necessary work of explaining the return shape, and a single-parameter read tool has little other complexity to cover. The remaining gap is failure/empty-case behavior for an invalid id.

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?

Only one parameter with 100% schema description coverage, so the schema carries the semantics ('Booking id from list_bookings'). The description restates 'by id' but adds no format, range or sourcing detail beyond what the schema already says; baseline 3 applies.

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 ('Reads a booking by id') and enumerates exactly what comes back (date/arrival window, customer, address, providers, service parameters and extras, notes, price breakdown, provider pay). This clearly separates it from list_bookings, which returns the ids this tool consumes.

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 'reads a booking by id' framing plus the schema's 'Booking id from list_bookings' makes the retrieval-after-listing workflow clear. There is no explicit when-not guidance (e.g. use list_bookings to search, use reschedule_booking to modify), so it stops short of full routing guidance.

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