aiworkhub_agent_cancel_task

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

No annotations are provided, so the description carries the full burden. 'Terminate' implies a destructive, likely irreversible operation, but the description never says whether the process is killed forcefully, what the two gates are, what happens if a gate fails, or whether authorization is required. 'DUAL-GATED' hints at a safeguard without disclosing its behavior.

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?

It is a single short sentence with the action front-loaded, which is efficient. But the terse 'DUAL-GATED' label consumes prime space with opaque jargon rather than information, so brevity here costs clarity.

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 destructive control-plane operation with no annotations and 0% schema coverage, the description leaves critical gaps: which task/process states are eligible, what the dual gate enforces, and what the effect on the recorded process group is. An output schema exists, so return values need not be described, but the operational contract is not.

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 0%, so the description must compensate, yet it only alludes to a recorded request without explaining the required request_id format, whether it must reference a live process, or what the 'reason' field's default 'owner_cancelled' means or which values are accepted.

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 verb 'terminate' and resource 'one exact process group recorded by this server' give a recognizable action, and the past-tense framing distinguishes it from aiworkhub_agent_list_processes (a read). However, 'DUAL-GATED' is unexplained jargon that an agent cannot decode, and the scope phrase 'recorded by this server' is vague about which server/bookkeeping is meant.

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?

There is no statement of when to cancel versus when to retry, recover, or leave a task alone, even though siblings such as aiworkhub_agent_retry_finalization and aiworkhub_task_stale_recovery_recommend exist. No prerequisites, no mention of which task state permits cancellation.

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