Payment QR for an invoice

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

The annotations already disclose that this is not read-only, not idempotent, and not destructive, so the description benefits from adding the data-source behavior: IBAN/name come from the shared business profile and invoice_id reads from the invoice store. However, it omits file-writing behavior and overwrite implications, and the phrase 'never asked for' sits awkwardly with the optional iban/name override parameters in the schema.

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 a single front-loaded sentence with no filler, and it prioritizes the main invocation path. It is somewhat dense and run-on, but it remains efficient for the amount of usage context it conveys.

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?

The core invocation path is explained well: amount/reference or invoice_id, with profile-sourced beneficiary data. For an 11-parameter generation tool with no output schema, however, it leaves out important output and file behavior such as inline SVG versus PNG output, Pro restrictions, and overwrite semantics.

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 11 parameters and the baseline is 3. The description adds useful defaulting semantics for amount, reference, and invoice_id, but it does not cover the output/file parameters and its 'never asked for' wording conflicts with the optional iban and name overrides.

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 resource and action: obtaining a SEPA payment QR, with the key scoping conditions of amount/reference or invoice_id. It also distinguishes this invoice-oriented flow from a generic SEPA QR tool by explaining that IBAN and name come from the shared business profile.

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?

It clearly says to use the tool with amount and reference, or to pass invoice_id instead when the amount should come from an invoice. It does not explicitly name when to use a sibling such as qr_payment_sepa instead, so the guidance is strong but not fully comparative.

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