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

Annotations only declare destructiveHint=true, so the description's disclosure that the result is a DRAFT and that no email is sent is genuinely useful side-effect context. It does not, however, address the surprising destructiveHint on a create operation, nor permissions, idempotency, or what happens to any pre-existing data.

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?

Two short sentences with the draft/no-email constraint front-loaded, plus a compact endpoint reference. No filler or 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 17-parameter mutation tool with no output schema, the description supplies the essential orientation (draft quote, no email, API route) while the fully documented schema carries the field-level burden. It could say more about the draft lifecycle (e.g., how the quote later becomes an invoice), but nothing required to invoke it correctly is missing.

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% and every parameter is documented in the schema, so the baseline is 3. The description contributes no parameter-level detail beyond the schema, only the generic mention of "for a client" which maps to the required client_id.

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 quote (estimate) for a client") and disambiguates the quote/estimate terminology. It also indirectly distinguishes itself from invoiceninja_create_invoice and invoiceninja_convert_quote_to_invoice by making clear this produces a draft quote rather than an invoice.

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?

The note "Nothing is emailed" gives the agent a clear condition for choosing this tool over emailing siblings like invoiceninja_email_invoice, and the DRAFT qualifier signals this is a preparatory step. However, it never explicitly names an alternative tool or states when a quote should be created versus an invoice.

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