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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds two useful behavioral facts beyond them: results are scoped to the caller's own codes, and pagination is cursor-based and stable. It does not explain traversal mechanics or termination, so it remains a modest addition.

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?

A single sentence with no filler; the ownership scope is front-loaded followed by the two capabilities (search, pagination). Every clause carries information an agent needs.

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 3-parameter list tool with no output schema and no parameter descriptions, the definition covers scope and the two main affordances but is silent on limit behavior, cursor lifecycle, and what fields come back. Annotations carry the safety burden, so this is adequate-but-incomplete rather than deficient.

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 0%, so the schema documents only types and constraints (UUID pattern, max 100), not meanings. The description compensates for two of three parameters by naming 'label search' and 'cursor pagination', but leaves 'limit' undefined and gives no cursor semantics (how to obtain or terminate). Partial compensation.

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+resource (list/find QR codes) and adds a scope qualifier: 'only your owned'. This distinguishes it from get_qr_code (single-item) and create_qr, though no sibling is named explicitly. Clear, but not maximally differentiated.

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 is only implied by 'Find only your owned QR codes' — an agent can infer this is the enumeration/search tool, but the description never says when to use it versus get_qr_code or how it relates to list-style alternatives. No exclusions or prerequisites are stated.

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