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

Goes well beyond the annotations (readOnly=false, openWorld=true, destructive=false) by disclosing that it holds the room, updates availability on connected channels, that unallocated bookings still reduce availability, that no confirmation email is sent, that card details are rejected, and that it reaches other people and needs a scoped API key. Rich, genuinely useful operational context.

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?

Core purpose is front-loaded, but the text repeats 'No card details' / 'Card details are not accepted' and mixes several loosely related caveats, adding avoidable redundancy to an otherwise information-dense block.

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 mutation tool with no output schema, the description covers the key things an agent needs: side effects on availability, email behavior, unallocated-room semantics, confirmation/reach implications, and auth prerequisites. Nothing material is missing.

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 coverage is 100% (baseline 3), and the description adds real meaning for room_id by explaining the consequence of omitting it ('unallocated but still reduces availability'), which the schema's terse 'Default: unallocated' does not convey.

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 ('Creates a Front Desk reservation') and adds scope detail (manual reservation, LH-prefixed booking reference). An agent can clearly distinguish this from siblings like list_reservations or update_reservation_status.

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?

Provides context that this is for manual Front Desk reservations and explains the room_id branch, but never names an alternative tool or states when NOT to use it (e.g., vs. booking via channels or other reservation tools). Usage is implied rather than routed.

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