delete-workflow

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

The description discloses that the action cannot be undone, which is a key behavioral trait. Since no annotations are provided, the description carries the full burden, and it adequately informs about irreversibility and the formatting requirement.

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: the first states purpose and consequence, the second is a critical usage instruction. No fluff, front-loaded, every word earns its place.

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 (2 required params, no output schema, no nested objects), the description covers irreversibility and a key formatting requirement. It could optionally mention success/error behavior, but it is sufficiently complete.

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% with descriptions for both parameters (id and clientId). The description does not add additional meaning beyond the schema, so it meets the baseline of 3.

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 'Delete a workflow by ID', which is a specific verb+resource. It distinguishes from sibling tools like activate-workflow, deactivate-workflow, create-workflow, etc., as it is the only delete operation for workflows.

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?

The description provides a critical usage instruction: 'Arguments must be provided as compact, single-line JSON without whitespace or newlines.' However, it does not explicitly state when to use this tool versus alternatives like deactivate-workflow, or when not to use it.

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