generate_payment_qr

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

No annotations provided, so description carries full burden. It states 'generate' implying a creation action, but does not specify if the tool is read-only, has side effects, or requires specific authentication. Lacks behavioral traits like whether it modifies the payment or returns a file.

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?

Description is concise: one sentence for purpose, then a structured 'USE THIS WHEN' list and examples. Front-loaded with purpose. Minor verbosity from examples, but they enhance clarity without being excessive.

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 no output schema, the description should explain return format (e.g., image data, URL). It does not. Also missing error conditions or prerequisites. Complete for usage scenarios but incomplete for expected output.

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 detailed parameter descriptions. The description adds no extra meaning beyond what the schema provides (e.g., no additional context for 'gateway_environment' when auto-detection happens). Baseline 3 is appropriate.

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?

Clearly states it generates QR codes for payment address/URI from an existing payment. Distinguishes itself from sibling tools (create_payment_link, create_payment_onchain, etc.) which focus on payment creation or status, not QR generation.

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?

Explicit 'USE THIS WHEN' section lists specific scenarios (different size/style, only address or URI, originally without QR, gateway URL) and provides example user requests. Effectively guides when to use this tool versus alternatives.

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