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

Adds substantial context beyond the annotations: the 7-day payment window, that sales tax is applied automatically (so the caller must not include it), the default per-call confirmation with an option to disable it, the warning to confirm with the user because it reaches other people, and the Cotlet API key requirement. This is exactly the mutation/authorization/rate context an agent needs.

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?

The purpose is front-loaded, but the middle is repetitive: 'The guest has 7 days to pay' and 'The guest then has 7 days to review and submit payment' restate the same window, and 'you confirm each call' overlaps with 'confirm with the user before each call.' Several sentences could be merged without losing content.

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, the description carries the return burden but still covers the outcome well (invite sent, guest's payment window), pricing rules, confirmation semantics, and auth. Only the concrete response shape after sending is left unspecified, which is minor for this operation.

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%, so the baseline is 3, but the description meaningfully extends it: it explains the conditional logic behind minimum_spend and gratuity (only for spaces with a food and beverage minimum) and warns against bundling sales tax with rental_fee/minimum_spend/add-on amounts.

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?

State a specific verb and resource ('Invite the guest to book with your date, time, attendees and price' / 'Sends an invite-to-book from a guest thread'), which clearly distinguishes it from siblings like peerspace_accept_booking_request and peerspace_request_booking_update. An agent can tell what this does without opening the 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?

It gives clear context for use - issuing an invite-to-book from a guest thread, with pricing rules that conditionally apply (spaces with vs without a food and beverage minimum). However, it never names a sibling alternative (e.g. accept vs. decline booking request) so the agent must infer when this is the right choice versus those.

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