freeagent_mark_invoice_as_cancelled

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

Without annotations, the description must disclose behavioral traits but fails to. It does not mention whether the action is destructive, requires authentication, or whether it can be undone. The brevity leaves the agent uninformed about side effects.

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. It is concise but may be overly brief, lacking important context. It earns a 4 for being succinct.

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 simplicity (one parameter, no output schema), the description is minimally complete. However, it does not cover preconditions, potential errors, or the effect on invoice status, which are important for correct use among sibling tools.

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 parameter has 100% schema coverage with description 'The invoice ID'. The tool description adds no extra meaning beyond that, so a baseline of 3 is appropriate.

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 the verb 'Cancel' and resource 'invoice', clearly indicating the action. However, it does not explicitly differentiate from sibling tools like mark_invoice_as_draft or mark_invoice_as_sent, which also change invoice state.

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 alternatives such as freeagent_mark_invoice_as_draft, freeagent_mark_invoice_as_sent, or freeagent_delete_invoice. The description lacks context on prerequisites or invoice status requirements.

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