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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds useful behavior beyond annotations: newest-first ordering, 50 items per page, account scoping, and a detailed list of returned fields.

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?

It is a single front-loaded sentence that starts with the core action before listing details. The field enumeration is somewhat dense, but since there is no output schema, most of it earns its place.

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 low-complexity list tool, the description is complete: it covers account scope, ordering, page size, returned fields, and code status. The schema covers the only parameter and annotations cover safety, so no critical information 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?

The input schema fully documents the single 'page' parameter with its range, so the baseline is 3. The description adds meaningful pagination semantics by specifying '50 per page,' which tells the agent how many records each page contains.

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 states a specific verb and resource: it lists QR codes saved in the signed-in account. It also specifies ordering, page size, and returned fields, making it clearly distinct from create, preview, and update siblings.

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 usage is implied by 'Lists the QR codes saved in the signed-in account,' but there is no explicit guidance on when to use this vs. preview_qr_code, update_code_destination, or other siblings. It provides context but no exclusions or alternatives.

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