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

With no annotations, the description carries the full behavioral burden, and it largely restates the name. It discloses that output is SVG but says nothing about whether this is a pure/side-effect-free generation, size or content limits, error behavior for malformed input, or whether the result is returned inline or as a file.

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 tight sentence with the output artifact front-loaded, no filler or redundancy. It is appropriately short for a small utility tool, though it is too sparse to be maximally informative.

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 simple, no-output-schema generator the description is minimally viable, and the nested wifi schema covers the structure. It omits the wifi-over-text precedence, the format enum, and any note on what the SVG return looks like, leaving those gaps to structured fields.

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 67% and the schema already documents text, wifi, and the wifi precedence rule. The description adds only a restatement of the accepted input categories and says nothing about the format parameter or the anyOf constraint beyond what the schema shows.

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 ('Make') and resource ('SVG QR code') and enumerates the three encodable payload types (text, URL, Wi-Fi), so an agent immediately knows what the tool produces. It does not name any sibling, but the sibling set (find_data, get_transcript, page_to_markdown, resume_gap) is so unrelated that differentiation is unnecessary.

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 the tool is useful (when you have text, a URL, or Wi-Fi details to encode) but gives no explicit when-to-use guidance, no exclusions, and no alternatives. Nothing tells an agent whether this is the preferred path versus generating a QR some other way.

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