Create estimate

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the record is created in draft state and no email is dispatched, which an agent could not infer from annotations alone.

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?

Four short sentences, front-loaded with the core action and result state. No filler, though the deposit sentence is vague about which parameters it maps to.

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 31-parameter mutation tool with low schema description coverage and no output schema, the description is far too thin. An agent gets no guidance on currency/exchangeRate interplay, discount scale verification, businessId defaulting, or what the created draft returns.

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 only 26% across 31 parameters, so the description carries a heavy compensation burden and does not meet it. It restates the two required line fields (already in the schema's required array) and mentions an optional deposit, but says nothing about currency, exchangeRate, discounts, businessId defaulting, or the many hide*/title* layout flags.

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 and resource ('Create a draft estimate (quote)') and clarifies the creation result is a draft. 'Nothing is emailed' implicitly separates it from wave_send_estimate, though no sibling is named explicitly.

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?

Usage is only implied: 'draft' and 'Nothing is emailed' hint that this is the pre-send creation step versus wave_send_estimate or wave_create_invoice. No explicit when-to-use, prerequisites, or named alternative is given.

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