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

With no annotations, the description carries the full behavioral burden and does disclose useful traits: static/non-expiring encoding, no redirect, and that output is a PNG image or SVG text. However, it omits auth/permission needs and, critically, which parameters are required per QR type despite 17 optional parameters.

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 compact sentences with the core action first and the differentiating static/return-format details immediately after. No filler or repetition.

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?

For a 17-parameter tool with no annotations and no output schema, this description is far too thin. An agent cannot tell which fields are required for each type, how the styling parameters interact, or what the returned image/SVG looks like, so it would likely need to guess or retry.

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 only 6% across 17 parameters, so the description should compensate and does not. It only indirectly touches 'format' (PNG/SVG) and 'data'; the type-specific groups (ssid/password/encryption for wifi, first_name/last_name/email/phone/org for vcard) and styling params (bg, fg, ec, size, hidden) are 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?

States a specific verb and resource ('Generate a static QR code') and adds a meaningful domain distinction between static and dynamic codes (never expires, no redirect, content encoded directly). Clear on its own, though there are no sibling tools to differentiate against.

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?

No guidance on when to use this tool or how to choose between the four supported types (url, text, wifi, vcard). The agent is left to infer that 'type' selects the payload mode and which fields each mode requires.

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