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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds the statement 'This is irreversible,' which reinforces the destructive nature but doesn't add substantial new behavioral detail beyond what annotations already convey. It does not contradict the annotations, so the baseline of 3 is appropriate given the low bar set by 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?

The description is two short sentences with no filler. It front-loads the action and then the critical warning about irreversibility. Every word earns its place, making it highly efficient.

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 (one required parameter) and that the annotations cover destructive and idempotent behavior, the description is minimal but not wholly incomplete. It does not mention potential side effects like cascading deletions of related checkpoints or executions, nor does it clarify behavior for non-existent ids. However, with the output schema present and the low complexity, it's acceptable but not thorough.

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 has 0% description coverage, so the description must compensate. However, the description only says 'by id,' which is redundant given the parameter name 'workflow_id.' It provides no additional context about the format, how to obtain the id, or any special constraints. This adds minimal value beyond the schema itself.

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 states a specific verb ('Delete'), a clear resource ('workflow'), and the identifier ('by id'). This unambiguously distinguishes it from sibling tools like create_workflow or update_workflow. The action is perfectly clear with no ambiguity.

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 offers no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. It only notes that the action is irreversible, which is a safety warning rather than usage context. An agent has no explicit direction on when deletion is appropriate.

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