Terminate A Workflow Instance (Project) (Public)

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

Annotations are sparse (readOnlyHint=false, destructiveHint=false). The description adds confusion by stating 'Creates a new Workflows' which is inaccurate for a terminate action. Does not explain side effects, prerequisites, or response behavior. The description contradicts the tool's expected behavior.

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?

Description is verbose with redundant first sentence, awkward grammar ('perform the terminate a action'), and an erroneous sentence about creation. It wastes space on API details that could be inferred from the endpoint.

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, so description should explain the result of termination (e.g., what happens to the instance, workflow transitions). It fails to describe return values or side effects, leaving the agent underinformed. The erroneous 'Creates' statement also misleads.

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 has 100% coverage with descriptions like 'URL path parameter — unique identifier for the company.' The description merely lists required parameters without adding meaning beyond what the schema already provides, meeting the baseline.

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 resource 'Workflow Instance', but includes a contradictory sentence 'Creates a new Workflows' which undermines clarity. It distinguishes from sibling by mentioning 'Project' in the title, but the erroneous create statement reduces confidence.

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 vs alternatives like respond_to_a_workflow_instance_project or the company version. The description only lists required parameters without context on use cases or exclusions.

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