Terminate A Workflow Instance (Company) (Public)

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

The description claims it 'Creates a new Workflows', which contradicts the annotations (destructiveHint=false). It does not disclose that termination is irreversible or requires permissions. The description contradicts the annotation's intent.

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 short but contains contradictory information and is poorly structured. It mixes creation and termination actions, reducing clarity.

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?

No output schema exists. The description claims HTTP 201 with a created object, which is inconsistent with termination. It does not explain failure scenarios or the actual return value for a terminate action.

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 coverage is 100%, so the schema already documents the parameters. The description merely restates required parameters and that they are URL path parameters, adding no additional meaning beyond the schema.

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 states it is used to 'perform the terminate a action on Workflows' but then says 'Creates a new Workflows', which is contradictory. It does not differentiate from sibling tools like respond_to_a_workflow_instance_company or restart_a_workflow_instance_company.

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 this tool versus alternatives. It does not specify prerequisites, when not to use, or any context for selection.

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