delete_workflow

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

No annotations provided; the description only states deletion and a restriction on bundled workflows. It does not disclose irreversibility, permissions needed, or side effects for a destructive operation.

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 concise sentences, no fluff, front-loaded with key information. 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?

The description covers basic purpose and a key constraint, but for a destructive operation it lacks details on error handling, idempotency, or behavior when workflow does not exist.

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?

With 0% schema description coverage, the description adds minimal value beyond the schema. It says 'by name' but does not clarify format, constraints, or what the name refers to.

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', the resource 'user workflow', and the qualification 'by name'. It also notes that bundled workflows cannot be deleted, which helps distinguish from other workflow tools.

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 implies use when deleting a user workflow, but does not explicitly state when to use versus alternatives like update_workflow or create_workflow. The bundled workflow limitation is useful but not a usage guideline.

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