list_qr_codes

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

With no annotations, the description carries the burden and does well by disclosing the auth requirement and plan gating (Developer plan) plus pagination and filtering behavior. It doesn't cover rate limits or default ordering, keeping it from a 5.

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, front-loading the primary purpose followed by capability and auth prerequisites—no filler.

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?

Given a simple read-only list tool with full schema coverage and no output schema, the description covers purpose, capabilities, and auth needs. Return format isn't explained, but for a straightforward listing tool this is largely adequate.

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% with per-parameter descriptions (page, limit ranges, type enum), so the schema does the heavy lifting. The description restates pagination and type filtering without adding format details, 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?

States a specific verb (List) and resource (QR codes) scoped to the authenticated user's account, clearly distinguishing it from generate_qr_code (creation) and get_analytics (analytics).

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?

Describes the context (account-scoped listing with pagination and filtering by type) and names a prerequisite (API key, Developer plan), though it doesn't explicitly state when to prefer this over get_analytics.

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