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

Annotations only carry destructiveHint=true and a title, so the description usefully adds that the created object is a draft, that no notification is dispatched, and that edits are non-final. It does not cover permission requirements or what happens to unset fields, but the draft/no-email disclosure is meaningful context beyond the structured hints.

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 tight sentences with the draft/no-email constraint front-loaded, plus the API endpoint for traceability. Very little waste, though the endpoint sentence is arguably redundant for an agent that only needs tool semantics.

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 create tool with one required field and full schema coverage, the description supplies the essential framing (draft state, no side-effect email). With no output schema, it could have noted what the response contains (e.g. the new quote id) for a follow-up call, which is the one remaining gap.

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 parameter meaning is already fully documented (including line_items replacement behavior and hashed-id formats). The description adds only "for a client," which does not extend beyond the schema's required client_id hashed-id entry.

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?

The description names a specific verb (Create) and resource (quote/estimate) and immediately pins the scope: it is a DRAFT, not a finalized or sent document. This separates it from siblings like invoiceninja_create_invoice and invoiceninja_email_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?

"Nothing is emailed" implies the agent should reach for invoiceninja_email_invoice (or convert_quote_to_invoice) as the next step, and implicitly contrasts with the draft-only path. But the when-to-use condition is only implied, with no explicit alternatives or preconditions (e.g. does the client need to exist first?).

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