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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful context that the response is a rendered image and that PNG is the default format, but says nothing about how the binary payload is returned or error behavior for a missing qrId.

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 front-loaded sentence wrapping verb, resource, and output formats with 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?

For a tool with no output schema, the description should explain the return shape (binary image vs. URL vs. base64) and the unexplained size parameter. It covers format selection but leaves these gaps for an otherwise simple read tool.

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 only 33%: qrId is documented in the schema and format is self-documenting via enum/default, both echoed by the description ('PNG (default) or SVG'). The 'size' parameter (64–4096) is unexplained in both schema and description, leaving a real gap.

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 ('Render') and resource ('a saved QR code') plus the output artifact type (PNG/SVG), which is more precise than the sibling get_qr_code or make_qr_code_image names alone. It does not explicitly name or contrast those siblings, so it stops short of a 5.

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?

The phrase 'saved QR code' implies this is for already-persisted codes rather than ad-hoc generation (make_qr_code_image), but the description never states when to use this versus get_qr_code or the make_* sibling. Usage must be inferred from the resource noun.

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