Delete PayPay QR Code

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

Annotations already carry destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds valuable behavioral context by stating the invalidation happens only before payment and cannot be used afterward. This goes beyond the structured annotations without contradicting them.

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 front-loaded with the core behavior and includes a clear use-case sentence. The Japanese translation doubles the length, but it is intentional localization rather than filler, so the structure remains efficient.

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 tool with rich annotations and no output schema, the description covers the essential operational context: purpose, timing constraint, and when to use it. It does not describe error behavior or return values, but those are less critical for this simple invalidation operation.

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 the code_id property is already documented as "The codeId returned from create_qr_code (NOT the merchantPaymentId)." The tool description itself adds no additional parameter-level meaning, so the baseline of 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?

The description states a specific verb and resource: "Invalidate a QR code before it is paid." It clearly defines the tool's scope and distinguishes it from siblings by emphasizing the pre-payment invalidation purpose, which separates it from create_qr_code, get_payment_details, and wait_for_payment.

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 gives explicit when-to-use guidance: "Use this when an order is canceled before checkout, or to clean up expired codes." It also states a clear exclusion: "Cannot be used after payment has completed," so an agent knows the boundary without ambiguity.

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