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

Annotations already declare readOnly/non-destructive/openWorld, and the description adds semantics beyond them: a booking leaves the list once acknowledged, the channel-manager interaction, and the auth requirement (Cotlet API key with app access). This is exactly the extra context the structured fields cannot carry.

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-loads the identity of the list before the behavior and the cross-reference. Slightly redundant: the first two sentences both restate that these are unacknowledged bookings waiting in the New Bookings tab, which could be merged.

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?

No output schema exists, and the description compensates by enumerating returned fields (booking reference, guest name, arrival date, booked date). Combined with the acknowledgement lifecycle and auth note, an agent has everything needed to call and interpret it.

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 limit (1-100, default 50) and cursor are already fully documented in the schema. The description adds nothing about pagination syntax or defaults, so the 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 (list) and resource (new bookings) plus a precise scope: bookings in the New Bookings tab not yet acknowledged. This clearly separates it from hostelworld_search_bookings and hostelworld_get_booking, so the agent can pick it without opening a 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?

Names an alternative and the condition that selects it ('Pass booking_ref to get_booking for full details') and gives a strong when-this-returns-nothing caveat (channel manager acknowledges bookings, so the list is usually empty). It stops short of explicitly contrasting with search_bookings for filtered or historical queries.

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