revoke_task

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

The description reveals that revocation can optionally terminate a running task via a signal (default SIGTERM). However, it omits details like whether the task is removed from queues, what happens to results, or required permissions. With no annotations, this is basic but incomplete.

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 very concise (11 words) and directly states the core function. While it could benefit from more structure, it is efficient for a simple tool.

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 presence of an output schema and the complexity of revocation, the description lacks crucial context: what 'revoke' entails (e.g., removing from queue), how it differs from abort_task, and the meaning of the signal parameter. The agent likely misses key behavioral traits.

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 explain all parameters. It only hints at the 'terminate' boolean effect, but 'task_id' and 'signal' are left undefined. This is insufficient compensation for a 3-parameter tool.

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 clearly states the action (revoke a task) and the optional behavior (terminate if running). However, it does not distinguish from the sibling 'abort_task', so the agent may not know which to use.

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 on when to use revoke_task versus alternatives like abort_task, nor any prerequisites or context. The agent receives no help in deciding when this tool is appropriate.

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