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

Annotations already flag destructiveHint=true and non-idempotent; the description adds the key detail that conversion mutates the code's type rather than creating a new code, plus a 'confirm with the user first' instruction. It stops short of saying whether the original vCard behavior, scans or short-link data survive the conversion.

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?

Three short sentences, front-loaded with the usage condition, then the mutation note, then the prerequisite. No filler and nothing an agent must hunt for.

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?

The tool is a single-parameter destructive conversion with an output schema and rich annotations, and the description covers the trigger condition, the type mutation and the confirmation requirement. A note on reversibility or downstream effects on existing scans would close the remaining gap.

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% and the parameter description already says 'ID of the vCard QR code from list_qrcodes. Never guess an ID.' The description repeats that same sourcing instruction without adding format or validation detail, 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?

States a precise verb+resource ('turn a vCard QR code into a digital business card page') and scopes it to codes already in the account, which cleanly separates it from create_digital_business_card. An agent can identify the operation without opening the schema.

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?

Gives an explicit precondition ('user already has a vCard QR code in their account') and a prerequisite step (get the ID from list_qrcodes). It does not name the sibling to use instead when the user has no vCard code yet (create_digital_business_card), which keeps it short of a 5.

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