Cancel Execution

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

With no annotations, the description carries the full burden of behavioral disclosure, and it discloses almost nothing. It does not state whether cancellation is immediate, whether it is idempotent, what happens to already-produced results or artifacts, or what the execution's resulting state will be. The only hint is the adjective 'running', which is helpful but far short of the needed context for a destructive operation.

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 sentence is front-loaded and free of padding, which is good, but at four words it is under-specified rather than truly concise. There is room to add scope and behavioral detail without becoming verbose.

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?

An output schema exists, so return values need not be described. Still, for a destructive mutation with no annotations and an entirely undocumented required parameter, the definition omits information an agent needs to invoke it safely and correctly.

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% and the single parameter execution_id has no documented format, source, or example anywhere. The description does not compensate, so an agent gets no help on where to obtain a valid execution_id (presumably from list_executions or get_execution).

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 names a specific verb (cancel) and resource (execution), so the operation is immediately identifiable. However, it offers no differentiation from sibling tools such as get_execution, list_executions, or stop_stream, which an agent must distinguish between when deciding what to call.

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 versus alternatives like get_execution or list_executions, nor any stated prerequisites. The word 'running' hints that only in-flight executions are cancellable, but that is left implicit rather than stated as a condition.

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