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

The description says 'Create' implying a write operation, but annotations declare readOnlyHint=true, causing a direct contradiction. Additionally, the description does not specify the return format or any safety concerns, which is a severe omission.

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, well-structured sentence that front-loads the core purpose and provides essential context about regional auto-selection. Every word contributes meaning without repetition.

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?

Despite high schema coverage and a clear purpose, the description omits the output format (likely a QR code image) and error handling. The contradiction with annotations also undermines completeness. It is adequate but has notable gaps.

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% with good parameter descriptions. The description adds value by explaining the auto-detection logic for standards and how parameters like bic and variable_symbol behave differently per standard, going beyond the schema.

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 tool creates a European payment QR code and explains the auto-selection between SPAYD and EPC/GiroCode based on IBAN region. It effectively distinguishes from siblings like qr_payment_batch and other QR generators by specifying its single-payment focus.

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 provides context on when to use it (European payment QR codes) and how it auto-selects standards based on IBAN. However, it lacks explicit comparison to qr_payment_batch and does not state prerequisites or when not to use it.

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