invoices_bulk_cancel

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description does add genuine value by disclosing partial-failure behavior ('any per-item errors') and the return shape, which annotations cannot express. It omits whether cancellation is reversible (an invoices_restore sibling exists) and any permission requirements.

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?

Two sentences, zero waste, with the core action front-loaded and the return behavior trailing. Nothing is repeated or padded.

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?

With no output schema, the description correctly compensates by stating the return value (count plus per-item errors). Combined with a fully documented input schema and rich destructive/idempotent annotations, an agent has nearly everything needed; only reversibility and batch-limit failure behavior are unaddressed.

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%, so all three parameters including the 1–100 id limit are already documented. The description only echoes the optional reason, adding no new semantics beyond the schema; baseline 3 applies.

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?

States a specific verb and resource (cancel) with the batch scope made explicit by 'multiple invoices in batch'. It is distinguishable from most siblings, though it never names invoices_cancel (single) or invoices_bulk_storno, which are the two nearest alternatives.

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 statement of when to use this versus invoices_cancel for a single invoice, or versus invoices_bulk_storno / invoices_bulk_delete. The word 'batch' implies multi-item usage but there are no prerequisites, exclusions, or alternative routing.

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