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

Annotations already declare destructiveHint=true, so the mutation warning is covered; the description adds meaningful context by disclosing that the source quote is marked converted and linked to the new invoice, and that the new invoice is returned. It stops short of covering authorization requirements or whether the conversion is reversible.

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?

One sentence covering the action, the side effect, and the return, followed by the endpoint reference. Front-loaded with zero waste.

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 one-parameter mutation with no output schema, the description supplies the side effect, the return value, and the endpoint, which is most of what an agent needs. Missing only prerequisite/eligibility conditions on the quote.

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% and the single quote_id parameter is fully documented with format example in the schema, so the description adds no syntax detail. Baseline 3 applies when the schema does the heavy lifting.

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+resource pair ('Convert a quote into a new invoice') and the endpoint, which cleanly distinguishes it from sibling creation tools like create_invoice and create_quote. An agent can identify this as the quote-to-invoice transformation without opening the 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?

Usage is implied by the conversion semantics and the side-effect note, but there is no explicit guidance on when to prefer this over invoiceninja_create_invoice or what prerequisite state the quote must be in. Adequate but leaves the agent to infer the trigger condition.

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