cancel_execution

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

The description discloses concrete behavior: 'SIGTERM all running workers and mark them failed.' This goes beyond the generic action of cancellation and provides useful operational detail, especially since no annotations are provided.

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, front-loaded with the verb, and contains zero wasted words. It is appropriately concise for the tool's simplicity.

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 simple tool with one parameter and no output schema, the description covers the essential action and effect. It could mention the post-cancel graph state, but it is adequate for selecting and invoking the tool.

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 description does not explicitly explain the graph_id parameter, but with only one parameter and a self-explanatory name, the meaning is inferable from the phrase 'a running graph.' The schema coverage is 0%, so the description partially compensates but could have been more explicit.

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 specific verb ('Cancel') and resource ('a running graph') to clearly state what the tool does. This distinguishes it from sibling tools like start_execution and create_graph.

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 includes a clear precondition ('a running graph') that tells the agent when to use this tool. While it does not explicitly name alternatives, the context is sufficient for a cancellation operation.

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