run_cancel

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

With no annotations, the 'Cancel' and 'stop active session' language indicates a destructive, state-changing operation. However, it lacks details on irreversibility, permission requirements, or effects on associated data, leaving some ambiguity.

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 sentence that immediately conveys the core action. It is front-loaded and contains no extraneous words, making it concise and efficient.

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?

Despite the tool's simplicity, the description omits important context: it doesn't clarify the parameter's meaning, state prerequisites, or mention output. Given no output schema and no annotations, it leaves gaps for the agent.

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 task_id is ambiguous (run ID vs task ID) and the description does not clarify it. With 0% schema coverage, the description should compensate but fails to explain the parameter's semantics or format.

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 verb 'Cancel' and the resource 'task run', and adds 'stop its active session' to clarify the scope. Among siblings like run_start, run_detach, and task_delete, it distinctly identifies its action on a run.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., run_detach or task_delete). It does not mention prerequisites, state requirements, or scenarios where cancellation is appropriate.

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