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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the return can be a 'link or pass' depending on provider, which is useful behavioral detail beyond annotations and beyond the schema, but it does not explain what a 'pass' is, its format, or any provider-specific constraints. Adequate, not rich.

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?

Two sentences, no filler, with the triggering condition front-loaded and the return behavior second. Every clause carries information the agent needs.

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?

An output schema exists, so the description needn't detail return values, and annotations cover the read-only/idempotent profile. The two required params are fully documented in-schema. Only provider-specific caveats (e.g. what happens if the QR type is unsupported by a wallet) are absent, which is a minor gap for a tool of this complexity.

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%: idqrcode references list_qrcodes with 'Never guess an ID', and provider is an enumerated field with apple/google semantics. The description adds nothing beyond 'for the chosen provider', so baseline 3 applies.

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 names a specific outcome (getting a wallet link/pass for a QR code) and the destination providers (Apple Wallet, Google Wallet), which lets an agent distinguish it from QR-generation siblings like generate_qr_code. It never explicitly contrasts with a sibling, but none in the sibling list shares this wallet purpose, so the gap is small.

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 opening clause 'Use this when the user wants to add a QR code ... to Apple Wallet or Google Wallet' gives a clear triggering intent rather than an implied one. It does not state exclusions or prerequisites (e.g. whether the QR code must already exist or be a wallet-compatible type), leaving some inference to the agent.

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