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

With no annotations present, the description carries the full burden of behavioral disclosure. It does disclose a meaningful consequence ('full refund') and the allowed task statesmaisn. However, it does not state whether cancellation is irreversible, how refunds are returned, or what happens to claims on the task. This is adequate but leaves significant behaviors implicit for a destructive financial action.

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 two short sentences, with the core operation front-loaded and the eligibility conditions immediately after. Every word contributes value; there is no redundancy or filler.

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, the essential inputs and eligibility are covered. However, the absence of an output schema and annotations means the agent is not told what happens after a successful cancellation, how errors surface when a task is not cancellable, or any side effects beyond the refund. It is usable, but not fully complete.

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 coverage is 50%: api_key is well documented in the schema, while task_id has only a type with no description. The description does not explicitly explain task_id, though 'Cancel a task' makes its role fairly obvious. The description adds little parameter meaning beyond the schema, but the lack of detail on task_id is partially mitigated by the tool's clear purpose.

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 a very specific verb and resource ('Cancel a task') and adds a key consequence ('for a full refund'). The state restriction ('Allowed while open, or while claimed-and-overdue') further differentiates this from sibling operations like approve, request_changes, or post_task, making it unmistakably the cancellation tool.

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?

It gives explicit conditions for when cancellation is permitted ('Allowed while open, or while claimed-and-overdue'), which tells an agent when this tool is appropriate. It does not explicitly name alternatives or state 'use X instead', but the allowed-state wording effectively excludes use in other situations.

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