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

No annotations are provided, so the description carries the full behavioral burden. It does not say what the tool returns (an SVG string, file, or URL), whether the operation has side effects, or whether the output format is fixed — it only echoes the format via the word 'SVG'.

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?

A single efficient sentence with the purpose front-loaded. The trailing vendor tag '(API Tool Calls, by Cowerx)' is boilerplate that earns no place in a functional description.

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 3-parameter generator with a nested wifi object, no annotations, and no output schema, the description is adequate but thin: it omits what the caller receives back and how the SVG is delivered, which matters because no output schema fills that 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 67%, so the schema already documents the text/wifi split and the wifi precedence rule. The description adds only the payload categories ('text, a URL, or Wi-Fi network details') and says nothing about the format parameter or the wifi sub-fields, leaving the gap partly unclosed.

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?

Names a specific verb (Make) and resource (SVG QR code) and enumerates the three payload types it accepts: text, URL, Wi-Fi details. It is distinguishable from make_barcode/read_barcode by the QR resource, but it never explicitly contrasts itself with those siblings.

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 by the payload list ('for text, a URL, or Wi-Fi network details') — there is no statement of when to choose this over make_barcode or any prerequisite/exclusion. An agent can infer intent but is given no routing guidance.

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