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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real context the annotations do not: the output is a rendered image plus the encoded link, and PNG is the default format when none is given. It omits how the image is delivered (inline vs. URL) and any auth/rate-limit notes.

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?

One tight sentence pair with zero filler, front-loaded with the action and resource before the format/size qualifiers and the return behavior. 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?

With no output schema, the description usefully states what comes back ('shows the image and returns the encoded link'), which is the key missing structured field for a render tool. It stops short of clarifying the image payload form (base64, content block, or URL), a minor remaining gap.

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% (only 'size' is described), so the description must compensate and it partially does: it supplies the missing default ('PNG (default)') that the enum lacks. The 64-4096 range duplicates the schema's minimum/maximum rather than adding meaning, and the required 'id' parameter is undocumented in both places.

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?

Specific verb+resource: 'Render a saved QR code with its design' tells the agent this returns an image artifact, and 'saved' implicitly separates it from qr_render_preview and qrs_get. However, neither sibling is named, so the agent must infer the boundary rather than being told it.

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: the agent can infer 'call this to obtain the image of an existing QR code by id.' There is no explicit when-to-use versus qr_render_preview or qrs_get, no note that the QR code must already exist, and no exclusion guidance, leaving the selection between the three render/get siblings to inference.

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