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

Annotations already declare non-read-only, open-world, non-destructive, so the bar is lower. The description adds real value by disclosing that the operation stays a draft, requires no user confirmation ('runs without asking first'), and needs the Cotlet API key with app access. It stops short of describing response shape or error behavior, but the auth and safety context is genuinely useful.

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 draft/no-send constraint is front-loaded and clear, and the API-key requirement is a useful trailing note. However, the draft state is stated twice ('Nothing is sent until you call send_quote' and 'stays a draft inside Tradify until send_quote'), which is 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 create tool with no output schema, the description covers the draft lifecycle, line-item types, expiry default, and auth requirements. It's nearly complete; only return/ID behavior is unaddressed, which is minor given the action-oriented nature of the 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 six parameters including line-item types and the expiry default. The description essentially repeats the schema's line-item types and expiry default rather than adding syntax or format detail. Baseline 3 is appropriate.

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 (creates a draft quote) and resource, and enumerates the line-item types (time, misc, price list, kit). It clearly distinguishes itself from tradify_send_quote and tradify_create_invoice_from_quote by emphasizing the draft state, so an agent can tell it apart from siblings.

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 frames the workflow: nothing is sent until send_quote is called, and the quote stays a draft. This routes the agent to the correct follow-up sibling. It doesn't state when NOT to use it or name a distinct alternative beyond the send step, so it falls just short of 5.

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