Create invoice from estimate

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool links documents and reports the proforma as invoiced, and warns against re-sending client/line items. It also specifies the return format. This adds useful behavioral context beyond annotations, though it could mention if the action is reversible or any permission requirements.

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 description is three sentences plus a short paragraph. It is front-loaded with the main purpose, followed by usage guidelines, and then parameter clarifications. No redundant information; every sentence serves a purpose. Could be slightly more compact but is already efficient.

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 tool with 10 parameters (1 required) and no output schema, the description covers purpose, behavioral effects, parameter hints, and return format. It provides sufficient context for an AI to decide when to use and how to invoke it. Missing explicit return value details beyond { series, number, url }, but that is enough.

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%, but the description adds meaning by explaining that client and line items are copied from the proforma (so not to be sent) and that seriesName is for the invoice while estimateSeriesName/estimateNumber identify the source. This clarifies the role of parameters beyond their schema descriptions.

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 clearly states the action (issue an invoice), the source (from a proforma/estimate), and distinguishes it from the sibling create_invoice by emphasizing that it links documents. The verb 'issue' and resource 'invoice from proforma' are specific.

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 advises preferring this tool over create_invoice when a proforma exists, and warns against manually rebuilding the invoice. It also notes that client and line items are copied, so they should not be re-sent. This provides clear when-to-use and when-not-to-use guidance.

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