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

With no annotations, the description carries the full burden, and it does disclose the cascade precisely: run history is removed and active runs are cancelled, while pipelines are unaffected. It says nothing about permanence or recoverability despite a workflow_deleted_restore sibling existing, nor about behavior when the id does not exist, so a key behavioral question for a delete tool is unanswered.

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, zero filler, with the primary effect front-loaded and the scope caveat immediately after. Nothing would be lost by keeping it exactly this size.

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 one-parameter destructive tool the definition covers the essentials an agent needs: what is destroyed, what side effect occurs, and what is untouched. The gaps are the recoverability story and the meaning of the id parameter, neither of which is filled elsewhere.

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 single required parameter 'workflow_id' has 0% schema description coverage and the description adds no meaning — not the expected id format, source of the id, or error behavior for an unknown id. With one undocumented parameter the description should compensate and does not.

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?

States a specific verb and resource ('Delete a workflow and its run history') plus a clear negative scope ('Pipelines are not touched'), which separates it from pipeline_delete and the workflow_deleted_* siblings. It stops short of naming the restore/list alternatives an agent may need, but the core action is unambiguous.

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?

Usage is implied rather than stated: the verb and the note that active runs are cancelled tell an agent this is the destructive path, but there is no explicit 'use this instead of workflow_run_cancel / workflow_deleted_restore' routing. No prerequisites or when-not conditions are given.

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