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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that line items, parties, and calculations are preserved during conversion, but it does not clarify persistence behavior or how the source document is treated beyond what the annotations imply.

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 definition is a single, front-loaded sentence with no wasted text. The verb and conversion outcome appear immediately, and the preservation clause adds useful detail without bloat.

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?

With an output schema and full annotation coverage, the description does not need to explain return values or safety flags. It covers the core conversion behavior, though it could note that the original payload is not modified and should align its target list with the enum that includes 'estimate'.

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. The description restates some target types but omits 'estimate' from the enum and adds no meaning for due_days, payment_link, credit_reason, or payment_qr_code. Baseline 3 is appropriate when the schema carries parameter semantics.

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 states a specific verb and resource: converting an existing document such as an Estimate or Quote into a Tax Invoice, Receipt, or Credit Note. It is clear what the tool does, but it does not distinguish itself from siblings like generate_document or preview_document.

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 'Convert an existing document', suggesting it applies after a document already exists. There is no explicit guidance on when to choose this over generate_document, preview_document, or calculate_totals, and no stated prerequisites or exclusions.

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