pennylane_finalize_customer_invoice

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds genuinely new behavioral context beyond the annotations: the action is irreversible and the invoice acquires a definitive number. It does not mention auth requirements or exactly which fields become immutable, keeping it short of a 5.

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 tightly-scoped sentences with no filler. The purpose is front-loaded and the irreversibility warning is given immediately after, in an easy-to-spot position.

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 single-parameter mutation with an output schema present, the description covers what the agent needs: what it does, that it is irreversible, and the numbering consequence. Minor gaps (auth/permission prerequisites, whether it can fail on an already-finalized invoice) remain but are non-blocking.

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% and there is only one parameter, whose meaning ('identifiant de la facture brouillon') is fully documented in the schema. The description adds nothing about the id beyond what the schema already provides, so the baseline of 3 applies.

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 (transforme/finalise) and resource (brouillon de facture client → facture finalisée), making the state transition explicit. This clearly distinguishes it from the sibling create_customer_invoice and update_customer_invoice tools without opening either 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?

The description implies the trigger condition (you have a draft to finalize), but never names an alternative or states when-not to use it. There is no explicit routing against update_customer_invoice or mark_customer_invoice_paid, so usage is only implied.

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