acedatacloud_cancel_invoice

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the caller-owned restriction and the confirmation requirement, which is useful, but it does not mention the consequences of cancellation (e.g., irreversibility, refund impact, or status changes).

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 short sentences with no filler or repetition. The essential information is front-loaded and every word earns its place.

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?

For a simple two-parameter tool with an output schema, the description is nearly complete: it states the action, scope, and safety precondition. It could add a note about post-cancellation effects, but it is adequate for an agent to invoke the tool safely.

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%, with both parameters documented: invoice_id as 'Invoice UUID' and confirm with 'Must be true to cancel the invoice.' The description's 'Requires confirmation' largely restates the confirm parameter, so it adds little beyond the schema.

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 uses a specific verb and resource: 'Cancel a caller-owned invoice.' It clearly identifies the operation and adds the 'caller-owned' scope, which helps distinguish it from sibling tools like get_invoice, apply_invoice, or preview_invoice.

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?

The description gives clear context: the invoice must be caller-owned and confirmation is required. It does not explicitly name alternatives or state when not to use it, but the cancellation purpose is obvious enough among the invoice-related siblings.

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