batch_cancel_invoice

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

The description mentions 're-submitting full invoice data with cancellation info', implying a mutation operation, but does not explicitly state that this cancels the invoice or disclose side effects like irreversibility. No annotations exist to clarify behavior. The description is sparse, only noting that it returns an API response.

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 concise and front-loaded, with a single sentence that conveys the basic purpose. It is not overly verbose, but it could include more information without significant bloat, such as clarifying batch behavior.

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 complexity of 31 parameters and no output schema or annotations, the description is insufficient. It does not explain the cancellation process, when to use this batch version, or any resubmission rules. A tool with many required fields demands more contextual guidance.

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?

The input schema has 100% description coverage, but many descriptions are cryptic codes (e.g., 'C2', 'A5'). The tool description adds no additional meaning beyond the schema. However, the phrase 're-submitting full invoice data' provides context that all parameters are needed to reconstruct the original invoice, which slightly aids understanding.

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 'Batch cancel an invoice', which clearly indicates the action and resource. However, the term 'batch' is ambiguous and not differentiated from the sibling tool 'cancel_invoice', which likely handles single invoice cancellations. The description lacks specificity about what the batch aspect entails.

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 is provided on when to use this tool versus other cancellation tools, such as 'cancel_invoice'. There is no mention of prerequisites, context, or scenarios where batch cancellation is appropriate. The description does not help the agent decide when to invoke this tool.

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