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

Goes well beyond annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false) by naming the concrete side effects: email sent to the property, room held until the owner answers or the request expires, guest emailed on reply, and the payment semantics (card held, charged only on acceptance). It also explains why the call is non-idempotent and what to do instead, which annotations alone cannot convey.

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 action and scope, and most sentences carry distinct information about side effects, idempotency and payment. Slight redundancy: the 'contract is directly between guest and property / Bookd is only the platform' point is repeated at the end as 'Bookd never handles guest money.'

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?

Although there is no output schema, the description supplies the return contract (booking_id, and payment_url when online payments are on), the side effects, the idempotency rule and the precondition set. For a 10-parameter mutating tool, that is sufficient for an agent to call it safely.

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 60%, so the schema already documents slug, room, check_in/out, message and creator_code. The description only restates the confirmed inputs (room, dates, guests, name, email) without adding format, ordering or constraint detail for the remaining parameters such as guest_phone or the guests range.

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 ('send a booking request') plus resource ('to the property ... for a room or unit and dates'), and it explicitly scopes the product role ('Bookd is only the booking platform'). An agent can distinguish this from check_availability (pre-check) and booking_status (post-check) 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?

Explicit precondition: 'Only call after the guest has confirmed the room, dates, guests, and given their name and email.' It also routes the agent away from retrying toward booking_status. The one gap is that it never states the obvious upstream dependency on check_availability to obtain a valid room name, which is only implied by the schema.

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