terminate_workflow

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

The description says 'forcefully terminate', implying a hard stop, but lacks details on side effects (e.g., activities are abandoned, state is lost), idempotency, or whether the action is reversible. With no annotations, the description carries full burden and falls short.

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 concise at one sentence, earning its place with a clear verb and resource. It could benefit from more detail, but it avoids unnecessary fluff.

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?

Given the simplicity of the tool and lack of output schema/annotations, the description omits important context: expected behavior, error states, and how it differs from cancel. It is adequate but not complete for an AI agent to use without risk.

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description adds no additional meaning beyond the schema; it does not explain the 'reason' parameter or provide usage context.

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 'terminate' and the resource 'workflow execution', making the core purpose unambiguous. However, it does not differentiate from sibling tools like 'cancel_workflow' or 'batch_terminate', which may confuse an AI agent on which tool to use.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., cancel_workflow for graceful shutdown, batch_terminate for mass termination). There is no mention of prerequisites or scenarios where this tool is appropriate or inappropriate.

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