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

No annotations provided, so description must fully disclose behavior. It only mentions output format but omits details like error correction level, size, supported character sets, or whether the tool is read-only. For a generation tool, users need to know if it's safe and what constraints apply.

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?

Description is extremely concise (9 words) and front-loads the core action. However, the brevity sacrifices necessary detail about parameters and behavior, so it is efficient but not optimally 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 2-parameter tool, the description minimally conveys the output format (SVG with base64 URI) but misses key details like the border parameter purpose and any limitations on input length or character encoding. It is adequate for basic usage but incomplete for thorough understanding.

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 0%, and the description provides no additional meaning for the two parameters (text and border). It fails to explain that 'border' controls the quiet zone width or that 'text' is the content to encode. The description adds no value beyond 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?

Description clearly states 'Generate QR code as SVG (base64 data URI included)' which specifies the action (generate), output format (SVG with base64 data URI), and distinguishes from sibling tools (none of which produce QR codes).

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 explicit guidance on when to use or avoid this tool, but the purpose is self-evident for QR code generation. No alternative tools exist among siblings, so differentiation is not needed. However, some context on typical use cases would improve score.

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