decode_qrcode_full

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

With no annotations provided, the description carries the full burden and discloses key behavioral details: it scans the entire image, returns all detected codes with diagnostics, and defines a result_code decision tree. It could further elaborate on what 'detailed diagnostics' includes, but the provided behavior is sufficient for an agent.

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?

The description is compact—three sentences that front-load the purpose, then present a terse decision tree. Every sentence contributes value, with no redundant or filler content.

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?

Given the lack of an output schema and annotations, the description provides a solid decision framework with result_code mappings. It could specify the exact output structure, but the guidance is enough for an agent to act on the tool's results.

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 100% with rich descriptions for each parameter, including usage precedence (e.g., image_path preferred over image_url) and examples for symbologies. The description itself adds no parameter information, but the schema already handles it, so a 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?

The description clearly states the tool scans the entire image for QR codes and decodes them, which is a specific verb+resource action. It adds that it returns all detected codes with diagnostics, distinguishing it from simpler or partial decode tools.

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 explicitly guides the agent on next steps based on result_code, including a direct alternative: 'RETRYABLE → call enhance_and_decode'. It also instructs to inform the user for NO_QR_FOUND or QR_UNRECOVERABLE, providing clear usage context and alternatives.

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