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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's 'stateless ... without mutating server records' largely restates that. It does add that a brand-new synthesized document is returned and that PDF synthesis occurs, but it omits anything on prerequisites, error conditions, or how credit_reason/due_days alter behavior.

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 sentences, front-loaded with the core verb and the stateless constraint, followed by a compact example call. The inline JSON example is slightly noisy but earns its place by showing the required payload shape.

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 present and full schema description coverage, the description does not need to explain return values, and it covers statelessness and the target types adequately. The main gap is the lack of any relation to the five sibling tools, which for a six-parameter tool in a crowded namespace is the missing piece.

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 every parameter is already documented in the schema, including the target_type enum, due_days being invoice-only, and payment_link QR embedding. The description adds only an example call showing document plus target_type; it contributes no semantics beyond the schema, which is the baseline-3 case.

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: it converts an Estimate/Quote JSON into another lifecycle document (invoice, receipt, credit note) statelessly and in memory. The scope is clear enough to distinguish it from mutation-oriented siblings, though the listed targets omit 'estimate' and 'refund' which the target_type enum actually supports, and it never names generate_document or preview_document as the alternatives.

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?

The phrase 'without mutating server records' implies the selection condition (use this when you want a throwaway synthesized document rather than a persisted one), and a concrete invocation example is given. However, there is no explicit when-to-use / when-not-to-use statement and no named alternative among the five siblings (generate_document, preview_document, calculate_totals, record_payment, get_pricing), so routing is left to inference.

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