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

With no annotations provided, the description must disclose behaviors itself. It does so by stating that static codes bake content into the code permanently, are not editable, and lack scan analytics. It also mentions the API key requirement. This covers persistence, mutability, and auth needs, but does not detail error scenarios, rate limits, or library interactions beyond 'save'.

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?

Three sentences, each adding value: purpose, static-vs-dynamic trade-offs, and usage requirements. The core action is front-loaded, and there is no redundant wording.

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?

The tool involves nested fields and multiple payload types, but the schema covers those. The description covers prerequisites (API key), the follow-up rendering step, and the permanence trait. It does not describe the return payload, but since no output schema exists, this is acceptable. Overall, an agent has enough to call it correctly.

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 input schema already provides 100% coverage with detailed per-type field descriptions. The description lists the supported payload types but does not add meaning beyond what the schema exposes. Since schema coverage is high, the baseline 3 is appropriate; the description doesn't compensate with extra parameter context.

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 clearly states the verb 'Save' with a specific resource ('static QR code') and a defined scope ('from structured fields'). It also distinguishes static from dynamic QR codes by mentioning the absence of short links and analytics, which differentiates it from sibling tool create_dynamic_qr.

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 description implies when to use this tool over dynamic QR by highlighting trade-offs (no short link, no analytics, not editable), and it gives a prerequisite (requires an OpenQR API key). It also provides a follow-up action (render with generate_qr). It lacks an explicit 'use this when...' statement, but the contrast with static vs dynamic is sufficient for an agent to infer selection.

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