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

Annotations are all false and provide no safety or side-effect hints, so the description carries the burden. It usefully discloses that IBAN and name are pulled from the shared profile and never requested from the caller, and that invoice_id can supply the amount. But it omits behavioral details like file generation, overwrite semantics, and the difference between inline SVG return versus expiring PNG download links, which are only revealed in parameter descriptions.

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 entire description is one dense, front-loaded sentence with no filler. It leads with the call-to-action, then immediately explains the two data-source behaviors that matter most, and avoids repeating schema details.

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 an 11-parameter tool with no output schema and no helpful annotations, the description captures the core scenario but leaves significant context to parameter descriptions. It does not explain the return payload shape or file-handling behavior, and it does not address the likely confusion with qr_payment_sepa. The rich schema compensates partially, but the description alone is not fully complete.

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%, so the baseline is 3. The description adds real meaning beyond the schema by explaining that IBAN and name are not needed from the caller, and that invoice_id can replace an explicit amount. This helps an agent understand the intended minimal inputs without reading every parameter detail.

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 operation: generating a SEPA payment QR from an amount and reference, with the unique twist that IBAN and name come from the shared business profile. This distinguishes it from generic QR siblings like qr_vcard or qr_wifi and even implies a different workflow from qr_payment_sepa.

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 gives a clear positive trigger ('Call this tool for a SEPA payment QR from just an amount and reference') and describes the invoice_id alternative for sourcing the amount. However, it never explicitly contrasts this with sibling qr_payment_sepa or states when NOT to use this tool, leaving some routing ambiguity.

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