qr_ecc_analysis

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

Describes the analysis performed (version estimation, codeword calculation, unused capacity reporting) and the steganographic purpose. No annotations exist, so description adequately covers behavior; no mention of side effects, but likely read-only.

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?

Three concise sentences, each adding value: function, what it calculates, and practical implication. No wasted words.

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 the tool's purpose and output (unused capacity report) but could be more specific about the format (e.g., numbers per level). With 3 parameters and no output schema, it is fairly complete.

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%, so schema already documents parameters well. The description adds no extra parameter detail beyond the schema, but provides context on the overall analysis output. 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?

Clearly states the tool performs error correction capacity analysis for QR codes, estimating version, calculating codewords per ECC level, and reporting unused capacity for steganography. This distinguishes it from siblings like qr_detect or qr_data_extract.

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?

Implies use for analyzing ECC capacity and steganographic potential, but does not explicitly state when to use this tool versus alternatives like qr_structure or qr_module_analysis. No exclusion criteria or context provided.

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