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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partially covered; the description adds real value by explaining this creates a Draft, that the client is not notified, and that a Cotlet API key with app access is required. It stops short of describing the response (e.g. estimate ID) but the behavioral context is solid.

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?

Front-loaded with the core action and generally efficient, but the 'nothing is sent' guarantee is stated twice and the Price Book item-matching rule is repeated, adding mild 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?

For a 3-parameter tool with full schema coverage and no output schema, the description covers purpose, draft/safety semantics, and auth requirements. The only notable gap is that it does not indicate what the call returns (e.g. an estimate ID needed for the follow-up send), though this is a minor omission.

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%, so the schema already documents client_id, items, and notes. The description restates that item names match Price Book items, which the schema field description also contains, so it adds little beyond the structured data. Baseline 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?

States a specific verb and resource ('Creates an estimate in Draft') plus the scope ('for one client' using Price Book items). An agent can distinguish it from workiz_send_estimate or workiz_create_invoice without opening a schema.

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 names the alternative and the boundary: 'Nothing is sent to the client until send_estimate runs, so this call runs without asking.' This tells the agent both when to use this tool and when the sibling applies.

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