verify_invoice_qr

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

With no annotations, the description carries the full burden and only says it validates a code. It does not disclose what validation entails (signature/hash check, lookup), what is returned on success or failure, whether this requires authentication, or how errors are surfaced. This is a significant gap for a verification tool with zero annotation coverage.

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 a single, front-loaded sentence with no filler; the purpose is stated immediately. It is appropriately sized for what it attempts, though the brevity reflects under-specification rather than efficiency in the other dimensions.

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 no annotations, no output schema, and 0% parameter description coverage, the description is not complete enough for an agent to invoke this tool confidently. It omits return behavior, error semantics, and the required input format for verification_code, all of which the structured fields do not provide.

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% for the single required parameter, so the description must compensate. It hints that the parameter accepts either an invoice dynamic verification hash or a B2B partner QR code, but does not specify the expected string format, whether QR content should be raw/base64/URL, or any length/encoding constraints.

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 states a specific verb ('Validates') and two specific resource types (invoice dynamic verification hash, B2B partner QR code), clearly distinguishing it from the sibling search, catalog, invoice-generation, and timesheet tools. It is clear what the tool does at a high level, though it doesn't say what a successful validation produces.

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?

There is no guidance on when to call this tool versus alternatives, no prerequisites, and no mention of the verification flow context. The verb implies a verification use case, but the agent gets no explicit conditions or exclusions.

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