render_qr

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

With no annotations provided, the description carries full burden. It discloses that the tool does not save the QR code (safe, read-only behavior) and returns either PNG image or SVG text based on the format parameter. This provides key behavioral context beyond what the input schema offers.

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 sentences: the first states the core function and key trait (no saving), the second specifies the output format. Every word is informative with no redundancy. The description is efficiently front-loaded.

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 tool with 4 parameters and no output schema, the description covers the main function and output types but lacks details on styling options, error handling, or links to related tools like list_qr_styles. The agent may need additional context to fully understand the tool's capabilities.

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 25% (only 'style' described). The description adds meaning by explaining that 'url' is for an arbitrary URL and that 'format' determines output type (PNG or SVG). However, 'size' and 'style' styling remain largely unexplained; the description could have elaborated on styling options or default values.

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?

The description clearly specifies that the tool renders a QR code for an arbitrary URL without saving it, distinguishing it from related tools like create_url_qrcode that create persistent QR codes. The verb 'render' and resource 'QR code' are specific and unambiguous.

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 implicitly suggests using this tool for quick, non-persistent QR code rendering, but does not explicitly list when to use or avoid this tool over alternatives like create_url_qrcode or get_qrcode_png. No explicit comparisons or conditionals are provided.

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