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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely new behavior: no account/free, static codes never expire and keep working without Snip, and the output is a PNG plus an SVG download link that should be shown to the user.

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?

Content type enumeration and the return-value/instruction sentence are front-loaded and each sentence earns its place. Slightly long, but nothing is padding.

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 correctly carries the return-value burden: it names the PNG and SVG download link and instructs the agent to show the PNG to the user. Combined with the usage routing, an agent has everything needed to call and present the result.

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 100%, so the baseline is 3, but the description adds meaning to the `data` parameter by naming the concrete accepted forms (WIFI:T:WPA;S:...;, vCard, mailto:, tel:, sms:) and routing changeable links to shorten_link. The bg/fg/ecc/style options are left entirely to the schema.

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 states a specific verb and resource ("Make a static QR code") and enumerates the supported content types (link, text, Wi-Fi, contact card, email, phone, SMS). It also distinguishes itself from the sibling shorten_link by noting that static codes hold content in the pattern.

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?

It gives an explicit trigger ("Use this whenever the user asks for a QR code") plus a routing rule to a sibling: use shorten_link instead for a link the user may want to change or track later. Both when-to-use and the alternative are named.

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