void_b2b_exchange_invoice

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

The description only states the action and that it returns the API response. It does not disclose side effects (e.g., irreversible changes), required permissions, error conditions, or rate limits. With no annotations provided, the description carries full burden but underdelivers.

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 concise sentence with no wasted words. It could be considered terse, but for a straightforward void operation it is appropriately sized, though it lacks structural elements like front-loading key info.

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 tool has 9 parameters (7 required) and no output schema or annotations, the description is too minimal. It does not explain the purpose of the 'A0201' code, typical use cases, or what the API response contains, leaving agents underinformed for proper invocation.

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 100%, and the parameter descriptions in the schema are clear (e.g., 'Cancellation date (YYYYMMDD)'). The tool description adds no additional meaning beyond what the schema already provides, meeting the baseline.

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 action 'Void (invalidate)' and the specific resource 'B2B exchange invoice (A0201)', distinguishing it from sibling tools like void_b2b_invoice and void_b2b_allowance. The inclusion of the document code adds precision.

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 guidance on when to use this tool versus alternatives (e.g., void_b2b_invoice), nor any context about prerequisites or conditions for voiding. Agents must infer usage from the tool name alone.

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