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

The description claims the server is 'Read-shaped tools only' and that anything which buys, sells or writes refuses, implying read-only behavior; the annotations set readOnlyHint=false. This is a direct contradiction. The description also provides no additional behavioral detail such as output format or error behavior.

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 opens with conceptual background, then contains an ungrammatical 'Because it —' fragment and irrelevant hosting/listing details ('live seat on The Wall', listing URL). It front-loads the wrong information and is not tightly structured.

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?

With no output schema, the description needed to explain what the tool returns (e.g., QR image, URL, data), how the reference is supplied, and any caveats. Instead it provides only conceptual context and a server-level constraint. The tool is callable with no params, but the behavioral contract is still under-specified.

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 tool has zero defined parameters and schema description coverage is 100%, so the schema already fully documents the parameter surface. The description's mention of `reference` adds background but does not need to document parameters; baseline 4 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?

The description explains that Singularity payment QR is artwork derived from a payment's `reference`, so one can infer the tool deals with receipt artwork. But it never states an action (retrieve/generate/render) or what input/output is expected, and it does not distinguish this from sibling singularityagent tools. This is vague rather than tautological.

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?

No guidance about when to call receipt_art versus alternatives. The 'Read-shaped tools only' sentence is a general server constraint, not a selection criterion, and 'Called through their seat' is about access, not usage.

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