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

Goes well beyond the annotations by disclosing permission tiers ('Write tier for the link; sending needs the full access level'), external side effects of the guarded SMS lane (STOP opt-outs and limits apply, recipient must be known to your org), and that messaging is external-facing. These are exactly the auth and rate-limit details an agent needs before triggering a send, and they are consistent with readOnlyHint=false and openWorldHint=true.

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 main action is front-loaded in the first clause, and every subsequent clause adds information (QR provenance, send routing, permission tiers, deprecated style). It is a single dense sentence packed with semicolons, which makes it slightly harder to scan than it needs to be.

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 three-parameter tool with full schema coverage, no output schema, and annotations covering the safety profile, the description covers everything material: what is produced (link + SVG QR), the optional delivery paths, the permission requirements, and the no-op `style` parameter. Nothing an agent needs in order to call it correctly is missing.

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%, so the nested `send` object, its message length cap, and the deprecated `style` field are already documented in the schema. The description adds routing semantics (phone/worker_id = text, email = e-mail) and the guarded-lane constraint, but largely restates what structured fields already carry, 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 verb and resource (get a task list's share link plus its QR code) and clarifies the QR is drawn by TaScan rather than a third-party service, which implicitly partitions it from tascan_generate_qr. The optional send behavior is spelled out clearly. It stops short of explicitly naming which sibling to use for standalone QR or unguarded SMS, so differentiation is inferred rather than stated.

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?

Usage context is concrete: call it to obtain the share link/QR, and add `send` only if you want to deliver it to one recipient, with the constraint that SMS recipients must be known to the org. There are no explicit exclusions (e.g., 'use tascan_send_sms for arbitrary numbers'), so the agent must infer the boundaries against the SMS/email siblings.

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