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

Annotations already declare it is a non-read-only, non-idempotent, non-destructive write, but the description adds the genuinely valuable workflow trait: this is a REQUEST the venue reviews and confirms, not an instant confirmation — an agent needs that to set user expectations and to handle polling via check_booking_status. It does not add auth/permission or rate-limit detail, so it stops short of a 5.

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?

Three short sentences, zero waste, with the scoping exclusion front-loaded in the first parenthetical and the request-vs-confirmation caveat placed last as the key behavioral takeaway.

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?

Covers purpose, alternatives, and the approval-workflow semantic, but for a 7-parameter, 4-required write tool with 14% schema coverage and no output schema, the description leaves most parameters unexplained and does not indicate what the request response contains or how to follow up.

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 only 14% — only 'datetime' is documented — so the description carries the burden and largely fails it. It mentions the venue's city/countryCode provenance (fields that do not even appear in the schema's properties) but says nothing about restaurantId, guestName, guestPhone, guestCount, guestEmail, or notes.

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?

Specific verb+resource ('Book a table reservation') with an explicit scope qualifier that rules out the closest sibling ('not a room/stay — use book_room for that'). An agent can distinguish this from book_room and book_service without opening any 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?

Explicitly names the alternative (book_room) and the condition that selects it, states the upstream dependency (city/countryCode come from search_venues), and sets expectations that this is a review-and-confirm request rather than an instant booking. When-to-use and what-to-use-instead are both covered.

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