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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds value by specifying what gets destroyed ('stored outputs') and that the action 'Cannot be undone,' which is richer than the bare destructive flag. It is consistent with idempotentHint=true and openWorldHint=true.

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 short sentences with zero filler; the scope ('workflow run and stored outputs') is front-loaded and the irreversibility warning comes second, before any parameter detail is needed. Every sentence 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?

For a simple 3-param delete tool the combination is complete: the schema documents all parameters, annotations carry the safety profile, an output schema exists, and the description covers scope and irreversibility. The only notable omission is a pointer to cancel_workflow_run for in-flight runs, which is a usage-guidance nicety rather than a correctness gap.

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 coverage is 100% — all three required parameters (runId, environment, workspaceId) carry their own descriptions, so the baseline is 3. The description adds no parameter-level detail, but it does not need to since the schema is fully documented.

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 ('permanently delete') and a precise resource ('a workflow run and its stored outputs'), and the qualifier '(workflows group)' positions it inside the workflow family. This lets an agent distinguish it from the many sibling delete_* run tools (delete_extract_run, delete_classify_run, delete_parse_run, delete_split_run) without opening their schemas.

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 explicit when/when-not statement, but the '(workflows group)' qualifier plus the run resource make the intended context clear among the run-deletion siblings. There is no exclusion note such as 'use cancel_workflow_run to stop an in-flight run instead,' so it stops short of a 5.

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