live_cancel_suite_run

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

With no annotations, the description carries the full burden. It discloses significant behavioral traits: 'force-interrupts whatever's actually in flight on every worker tab right now' and 'stops every worker from picking up anything further off the queue', which gives a clear picture of the impact although it doesn't mention edge cases like already-completed runs.

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, well-structured sentence that leads with the action and resource, then provides necessary details, with no redundant words.

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?

The description effectively conveys the purpose, behavior, and scope of the cancellation, including worker effects and queue stopping. It doesn't mention return values or error handling, but for a cancellation operation the provided context is sufficient.

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 schema already covers project and session with descriptions, but runId lacks a description. The description clarifies runId as the identifier of the suite run, adding minimal semantic value beyond the name; overall, it does not significantly enhance parameter understanding beyond what is already provided.

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 ('Cancels') and the resource ('suite run'), and differentiates from the sibling live_cancel_scenario_run by specifying 'by its runId' and 'same as live_cancel_scenario_run does for a single scenario run', making its purpose unambiguous.

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 provides explicit usage guidance by specifying the condition ('still-running suite run') and points to the alternative for single scenario runs, telling the agent when to use this tool versus a related one.

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