Send a Setell quote

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

Discloses irreversibility (aligns with destructiveHint=true), the pricing-analyst pre-check behavior (409 response), and the atomic guard conditions. Adds context beyond annotations by explaining the pushback response structure and the safety floor, without contradiction.

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 dense with information but could be better structured (e.g., bullet points for steps). However, every sentence adds value, and the most critical info (irreversibility, token requirement) is front-loaded. Slightly verbose but acceptable.

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?

Given no output schema, the description thoroughly covers the 409 response format, retry mechanism, and guard conditions. It conveys the full workflow context including operator responsibility and statefulness. Complex tool, high completeness.

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%, but description adds critical constraints like recipientEmail must match compose call, confirmationToken has 15-minute TTL and is bound to a specific version, and acknowledgePricingWarning requires a prior pushback verdict. This significantly enhances parameter understanding.

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 clearly states the tool 'IRREVERSIBLY sends the doorbell email to the customer' with specific verb and resource. It distinguishes from sibling tools like setell_compose_quote by highlighting the dependency on a confirmation token and from setell_schedule_send by being an immediate send.

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 states when to use: after obtaining a valid confirmationToken from setell_compose_quote. Provides detailed retry logic for pricing pushback, requiring operator confirmation before setting acknowledgePricingWarning. Mentions conditions where the guard rejects (revision, recipient drift, expired token, cross-tenant replay), guiding when not to call.

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