terminate_workflow

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

No annotations provided; description only says 'forcefully terminate' but does not disclose side effects (e.g., whether it kills running activities, irreversible, or required permissions). Minimal behavioral disclosure.

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?

Single sentence is concise and front-loaded, but lacks structure (e.g., separate sections for usage, effects). No wasted words, but could be organized better.

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?

Simple tool with only 2 parameters fully described in schema. However, termination is a critical action; description misses irreversible consequences or result behavior (no output schema). Adequate but not comprehensive.

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 covers both parameters with descriptions (100% coverage). Description adds no extra meaning beyond schema; baseline score of 3 is appropriate.

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?

Description clearly states the action and target ('forcefully terminate a workflow execution'). It distinguishes from basic query tools but does not differentiate from cancel_workflow, which may have a different semantic.

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 on when to use terminate vs cancel or other workflow lifecycle tools. Agent must infer context from sibling names without explicit conditions.

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