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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds real behavioral context beyond them: the estimate is saved as a draft and never sent, scheduling triggers customer notification per profile settings unless notify_customer is false, and an API key with app access is required. The per-call confirmation boilerplate adds little.

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 first two sentences are near-duplicates ('Create a draft estimate...' vs 'Saves a draft estimate... with a first option and its lines'), and the trailing confirmation/API-key boilerplate is generic. Tightening would remove real redundancy.

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?

No output schema and annotations cover the safety profile, so the description fills the important gaps: draft-not-sent behavior, notification side effects, the alternative tool for tiers, and the auth requirement. It is largely complete for a single-object mutation tool.

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 all 7 parameters with useful hints (defaults, price_book_id linkage, enum values). The description only restates the 'first option and its lines' shape, adding little semantics beyond 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?

States a specific verb ('Create a draft estimate') plus resource ('for a customer with a first option and its line items') and scope. It distinguishes itself from siblings by naming add_estimate_option for further tiers and clarifying the estimate is a draft that is 'not sent' (vs send_estimate).

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?

Routes the agent explicitly to add_estimate_option for additional tiers and clarifies the draft/not-sent state, which affects when to use it. It does not explicitly point to send_estimate for delivery or state prerequisites beyond the API key, so it falls short of full when/when-not coverage.

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