workflow_terminate_workflow

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

No annotations provided. Description says it stops and marks as terminated, but does not disclose whether termination is irreversible, fails if already terminated, or triggers side effects. For a destructive action, more disclosure is needed.

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?

Two sentences with immediate purpose and parameter details. No filler; every word serves a purpose. Very efficient for an AI agent.

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 output schema exists for return value, description adequately covers purpose and key parameters. Minor omission: no mention of error cases or prerequisites, but tool is simple enough.

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?

Description explains workflow_id as UUID of execution and reason as optional, adding meaning beyond schema types. With 0% schema coverage, this compensates well, though constraints on workflow_id format are missing.

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 it terminates a workflow execution and marks it as terminated. The verb 'terminates' and resource 'workflow execution' are specific. Among siblings like pause, resume, restart, this is distinct in action and finality.

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 explicit guidance on when to use vs. alternatives. The description implies termination is final, but doesn't contrast with pause or retry. Agent might need to infer context from sibling names.

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