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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real context beyond that by stating the effect precisely — ownership transfers from the anonymous creator to the account — which is the one thing the hints cannot convey. It omits whether the receiving account must be authenticated and what happens if the code is already owned.

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, no filler, with the restrictive usage condition and the effect front-loaded before the prerequisite. Every sentence carries independent information.

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 mutation tool with annotations and an output schema, the description supplies the trigger condition, the required inputs, and the resulting effect. The remaining gap is auth/precondition handling (must the target user be signed in, what if the code is already transferred), which matters for a destructive transfer.

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%, including the either/or requirement between idqrcode and shorturl_key, so the schema does the heavy lifting. The description restates 'ID or short-URL key' without adding format or syntax detail, and never mentions the optional idproject parameter. 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?

Names a specific verb+resource (transfer a QR code) and scopes it tightly: only for QR codes created by an unsigned-in user that must be moved into an account. That scoping condition implicitly separates it from move_qrcode_to_project and update_qr_code, though no sibling is named outright.

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?

"Use this only when..." gives both the selecting condition and an explicit restriction, and "Needs the code ID or short-URL key" tells the agent what input the call depends on. It stops short of naming the closest alternative (move_qrcode_to_project) for codes that are already owned.

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