bus_cancel_task

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

With zero annotations provided, the description is solely responsible for behavioral disclosure. Simply stating 'Cancel' provides almost no operational context regarding preconditions or guaranteed outcomes.

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 extremely concise and avoids any unnecessary filler, communicating the tool's function in a single, highly dense sentence.

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 tool within a large suite of task management functions, the description is insufficient. It lacks detail about preconditions, such as ensuring the task is indeed 'open' before cancellation.

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 input schema has 0% description coverage, and the description fails to provide meaning for the required parameters 'id' or 'agent'. The agent must infer what these IDs represent.

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 direct action verb and identifies the specific resource (open task) being manipulated. This provides clear semantic intent.

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 guidance on when to use this tool relative to similar state-changing siblings, such as bus_complete_task or bus_claim_task, forcing the agent to guess the correct workflow.

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