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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description adds meaningful traits: it returns the recipient and expiry, it contacts external people so user confirmation is expected before each call, a per-tool confirmation toggle exists, and it requires a Cotlet API key with app access. These are exactly the operational details annotations do not 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?

The confirmation and auth notes are valuable and front-loaded, but the first two sentences are near-duplicates ('Email a saved quote with an expiry date, reminder and optional offer' vs 'Emails a quote... with an optional expiry date, reminder and offer'). This redundancy weakens an otherwise well-structured 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 send action with no output schema, the description covers the essentials: what is sent, to whom, return values, auth requirement, and the confirmation obligation for reaching external people. It is nearly complete, missing only edge-case behavior such as failures or invalid quote IDs.

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 all five parameters (quote_id, to, offer, expires_on, reminder_days) are already documented in the schema. The description references the expiry, reminder and offer fields but adds no format or default detail beyond the schema, so the baseline of 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?

The description names a specific verb and resource: email a saved quote to the customer. This is unambiguous and an agent can tell it apart from read/list tools like list_bookings or get_provider_payments. It stops short of a 5 because the redundant second sentence restates the same purpose rather than sharpening the distinction from any sibling.

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 implies the usage context by specifying that the quote must be 'saved in the drafts and quotes folder', which tells the agent what input to prepare. However there is no explicit when-to-use versus when-not guidance and no named alternative among the bookingkoala siblings.

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