Send a quote

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

Beyond annotations, the description discloses the side effects: it saves the recipient and expiry date on the quote, emails the store template or supplied subject/message, and sends immediately. It also explains the failure mode for non-quote drafts. These details are consistent with readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=true.

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 description is front-loaded with the core action and remains reasonably concise. It repeats some schema-provided defaults, which is useful but slightly redundant.

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 mutating, non-idempotent email action with full schema coverage and no output schema, the description covers the important context: what is sent, what is saved, defaults, preconditions, and immediate delivery. Nothing essential for correct invocation 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 description coverage is 100%, so the schema already documents every parameter and its default. The description restates the key defaults for email and expires_on but adds little parameter meaning beyond what is already in the schema.

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 states a specific verb and resource: email a saved quote to the customer with a booking link. It also identifies the source collection, list_drafts, and distinguishes sendable quotes from plain drafts, so an agent can tell exactly what this tool does.

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 a clear precondition: only drafts saved as quotes can be sent, and a plain draft is refused before confirmation. It does not explicitly compare against all sibling tools such as resend_invoice, but the quote-specific context is strong.

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