Delete workflow

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

Annotations already indicate destructive and non-idempotent behavior. The description adds crucial context: 'no rollback or transfer', requires 'unsafe mode plus delete permission', and the exact response format ('returns the request-bound workflowId with deleted=true'). This goes beyond annotations.

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?

Three dense sentences, each earning its place: purpose, ID requirements, alternatives, consequences, permissions, and return value. No filler or redundancy.

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?

For a simple 1-parameter delete operation with a single required param and output schema, the description covers all necessary aspects: action, input requirements, alternatives, side effects, permissions, and response. There are no missing gaps.

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?

The schema already describes workflowId as 'Stable ID of the workflow to delete' (100% coverage). The description adds significant semantic value by specifying the ID source (from list or get) and excluding name/version IDs, which is not evident from 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 clearly states the action: 'Permanently delete one workflow and its saved definition.' It specifies the exact resource (workflow) and the permanent nature, distinguishing it from related tools like archive.

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?

Explicit guidance is provided: workflowId must be the current stable ID from list or get, not a name or version ID. It also directs users to alternative tools (archive for reversible removal, get for inspection), making when-to-use extremely clear.

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