Generate a QR code (SVG)

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

Annotations indicate readOnlyHint=true, so agent already knows it's safe. Description adds that output is 'crisp, dependency-free SVG', clarifying the return format. No contradictions. Does not disclose additional traits like rate limits or auth needs, but given simplicity and annotations, it's sufficient.

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?

Single sentence that efficiently conveys purpose and output format. No wasted words. Front-loaded with key information.

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 description covers what the tool does, the output format (SVG), and usage scenario. No output schema exists, but the description sufficiently describes the return. The 3 parameters are well-documented in schema. Minor gap: does not mention that text is required or max length, but that's in schema. Overall complete for a simple tool.

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 100%, so schema already explains all parameters (ecc, size, text). The tool description does not add any extra information about parameters beyond what's in the schema. Baseline 3 is appropriate.

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?

Description clearly states the tool's function: encoding text or URL into a QR code SVG. Uses specific verb 'Encode' and resource 'QR code SVG', and distinguishes from sibling tools which are unrelated (image_format_savings, optimize_image, storage_capacity).

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?

Provides context for use: 'paste straight into a page, deck or doc'. Does not explicitly exclude use cases or compare with siblings, but the sibling tools serve different purposes, so no exclusion is necessary. Lacks explicit 'when not to use'.

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