delete_workflow

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

The description only states 'Delete a workflow by ID' and fails to disclose important behavioral traits. It doesn't mention that associated notification channels may be deleted (as indicated by the delete_channels parameter), nor does it clarify whether deletion is permanent or requires special permissions. With no annotations, this gap is significant.

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 a single, concise sentence that front-loads the action. It wastes no words. However, it could be slightly improved by including the parameter nuance without losing conciseness.

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 lack of annotations and output schema, the description is insufficient. It omits important context such as the cascade effect of delete_channels, return value (if any), and prerequisites. The tool has only two parameters with full schema coverage, so more detail is expected.

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 description coverage is 100%, so the schema already fully describes both parameters. The description adds no additional meaning beyond the schema. It does not explain, for example, that delete_channels defaults to true, which would be helpful context.

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 'Delete' and the resource 'a workflow by ID'. It directly conveys the core action. However, it does not differentiate from other delete tools in the sibling list (e.g., delete_alert_policy) by explaining what a workflow is, but the name suffices for basic understanding.

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 like create_workflow, update_workflow, or other delete tools. The description lacks context on prerequisites (e.g., need to fetch workflow ID) or scenarios where deletion is appropriate.

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