Render a QR template

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the phrase 'for this specific call' usefully clarifies that overrides are ephemeral and the template itself is not mutated. It stops short of describing the rendered artifact's return shape, though an output schema exists for that.

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 front-loaded sentence that first establishes the core action (render template by id), then the optional adjustments. No filler, though it is dense enough that the override list reads as a run-on.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description adequately covers the override behavior for an 8-parameter tool; the only real gap is not pointing at qr_list_templates as the id source in the prose.

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 description groups the 8 parameters into meaningful categories (content, colors, output format/size) and frames them as overrides, which adds some meaning. But at 75% schema coverage the schema already documents these fields with defaults and ranges, so the description mostly restates them without adding format or constraint detail.

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 (curated templates by id), which distinguishes it from qr_generate and qr_generate_ai at a glance. It does not explicitly name those siblings, so the differentiation is inferred rather than stated, keeping it 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?

Usage is only implied: render a template when you want a curated design, and the overrides apply per-call. It never says when to prefer this over qr_generate or qr_generate_ai, nor does it state that a template id must first come from qr_list_templates (that hint lives only in the schema).

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