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

In the absence of annotations, the description discloses several behavioral traits: the response consists of one pre-formatted markdown table per QR code with the exact display instruction 'do not reformat or summarise', and authentication is required. However, it does not mention that results are paginated via page/limit parameters, which is a notable omission for a 'list all' tool.

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 description is very concise: two sentences that state purpose and then the return format/display instruction. Every sentence adds value, and the instruction about displaying tables exactly as received is crucial for agent behavior.

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 description covers the essential information: what it does, what it returns (fields and format), and the authentication requirement. Given that there is no output schema, this is quite helpful. It is missing explicit mention of pagination limits, but for a list operation with optional parameters, the description is sufficiently complete.

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 already describes both parameters (page and limit) with their defaults and maximums, achieving 100% coverage. The description adds no additional meaning about these parameters, so it meets the baseline for schema-covered parameters.

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 uses a specific verb 'List' with a clear resource 'QR codes' and scope 'in your account', which directly distinguishes it from sibling tools like get_qr_code (singular fetch) and mutation tools like create_qr_code, delete_qr_code, and update_qr_target.

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?

It states the tool lists all QR codes, providing clear context for when to use it. It does not explicitly name alternatives or mention when not to use it, but the phrase 'all QR codes' implies it is for enumeration rather than singular retrieval. Still, it does not address pagination or the difference from get_qr_scans, so it is not fully explicit.

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