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

Annotations already establish non-read-only and non-destructive. The description adds key behavior: output is a new draft (not finalized), source status precondition, and that id and total are returned. It does not cover duplicate conversion or whether the quote's status changes.

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?

Three compact sentences ordered as action, precondition, follow-up, and return value. Every sentence adds operational information.

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 conversion tool with no output schema, the description covers preconditions, resulting state, next step, and key return fields. Minor gaps around duplicate prevention and source-quote mutation keep it from being fully complete.

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?

With schema coverage at 0%, the description partially compensates by requiring the referenced quote to be in accepted status. However, it never names quote_id or clarifies the integer identifier format/behavior, leaving a gap.

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 (convert), source (accepted quote), and target (new draft invoice) with retained customer/items/rates. It also names the follow-up sibling finalize_invoice, making the boundary clear.

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 requires the quote to be in accepted status and tells the agent to review the resulting draft before calling finalize_invoice. It does not state what to do for a non-accepted quote or when to use create_invoice instead, so it stops short of full alternative routing.

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