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

Annotations already declare readOnly/no-destructive, so the bar is lower; the description adds auth context ('Needs the user's Cotlet API key with access to this app') and clarifies the payout-after-service-fee and request-expiry semantics. It does not cover rate limits or pagination, but contributes real value beyond the annotations.

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?

Front-loaded with the key information, but it repeats the same payload twice (add-ons, price, payout listed in both the first and second sentences), which is wasted space. A tighter single enumeration would serve better.

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 and annotations covering the safety profile, the description usefully enumerates the returned fields and the request-expiry nuance, which is what an agent needs to use the result. Only minor gaps around pagination or error behavior remain, appropriate for a simple read tool.

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 the single booking_id parameter is already fully documented in the schema. The description reinforces that the ID may refer to either a booking or a request, but adds little syntax or format detail beyond the schema; 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+resource ('Returns the full record of one booking or request') and enumerates the content returned (times, attendees, add-ons, price, payout, expiry). The singular scope distinguishes it from list_bookings, but no sibling tool is named explicitly, keeping it just short of a 5.

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?

'Read it before you accept or decline' gives a concrete usage trigger tied to the accept/decline workflow. It doesn't name the alternative siblings (accept_booking_request, decline_booking_request) or state exclusions, so it is clear context but not fully routing.

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