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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful trait — statelessness ("Nothing is stored") — but says nothing about how the PNG is returned (bytes, base64, URL) or whether rate limits apply.

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?

Two tight sentences with the capability front-loaded and no filler. Re-listing all ten enum values largely duplicates the schema, which costs a little density, but the sentence still earns its place.

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 7 parameters at 0% schema coverage and no output schema, the description should describe the return payload and at least the non-obvious inputs (e.g. color format, includeText behavior). It covers almost none of that, leaving the agent to infer invocation semantics.

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% across 7 parameters, so the description must carry the burden and does not. It repeats the format enum already present in the schema and adds no meaning for data, scale, height, background, foreground, or includeText.

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), resource (1D / retail barcode), enumerates supported symbologies, and names the output artifact (PNG). Combined with the 1D/retail framing, an agent can distinguish it from the sibling qr_render_preview without opening either schema.

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?

"Nothing is stored" implies this is the stateless rendering path as opposed to the persistent qrs_create* siblings, but no alternative is named and no when-not condition is given. Usage is implied rather than stated.

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