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

No annotations are provided, so the description carries full burden. It adds useful return-field details (ID, name, type, short URL, active status, creation date) but omits ordering, pagination behavior beyond schema defaults, or read-only confirmation. It does not contradict any annotation.

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, front-loaded with 'List QR codes', and each sentence carries meaningful content. No fluff or redundancy; efficient and well-structured.

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 list tool with no output schema, the description adequately covers return fields and usage context. It could mention response ordering or total count, but the simple tool and schema details make this sufficiently complete for an agent.

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%, so baseline is 3. The description adds no extra parameter semantics beyond what the schema already documents (type filter, limit, offset). It does not repeat or expand on them, but the baseline holds.

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 clearly states the tool lists QR codes in the user's Quality QR account, with a specific verb and resource. It differentiates from sibling tools like quality_qr_get (single retrieval) by emphasizing the list operation and enumerating returned fields.

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?

Provides explicit 'when to use' guidance: to see existing codes, find a specific code, or check count. It lacks when-not/alternative recommendations (e.g., for a single code use quality_qr_get), but the context is clear and enough for most agents.

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