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

With no annotations, the description discloses key behavioral traits: it is the anonymous shelf, identical to what a signed-out visitor sees, and codes may 403 on claim. This goes beyond a bare purpose statement, though it doesn't cover aspects like pagination or response structure (not critical for a 0-param list).

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 focused sentences, with the core function stated first. Every clause earns its place: the anonymous-shelf clarification, the usage suggestion, and the cross-reference to the sibling tool. No fluff or redundancy.

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 0-parameter tool with no output schema, the description covers what it does, who it's for, when to use it, and a critical limitation (403 on claim). It also points to the correct alternative, making it self-sufficient for the 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?

The schema has zero parameters, so there is nothing to explain. The description adds relevant context about the selection scope ('one per style') and preview image URLs, which is more than enough given the parameter-free interface.

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 opens with a precise verb and resource: 'List the QR artwork currently claimable for free on qart.uk, one per style, with a preview image URL for each.' It fully differentiates from sibling tools by explicitly naming browse_my_pool as the signed-in alternative.

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?

Clear usage context is provided: 'Use it to show someone what is available or to describe the styles on offer.' It also gives explicit when-not guidance, warning that signed-in accounts should use browse_my_pool instead to avoid 403 errors, and explains why.

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