delete_workflow_runs

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

The description indicates a destructive action, but without annotations it does not disclose whether the deletion is permanent, whether it affects the workflow definition, or whether confirmation is required. Behavior beyond the basic 'delete' verb is not explained.

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 with no redundant content. It directly conveys the essential purpose without unnecessary words.

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 tool is simple, but the description lacks important contextual details such as effects, irreversibility, and how it differs from closely related tools like undo_workflow_run or delete_workflow. With no annotations or output details, the description alone is not fully self-sufficient.

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 parameter workflow_id is mentioned in the description via 'd'un workflow', but the schema provides no per-parameter description. The meaning is mostly inferable from the parameter name and tool description, but no additional detail such as format or constraints is provided.

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 action: deleting the run history of a workflow. It also implicitly distinguishes itself from delete_workflow and undo_workflow_run by targeting the run history rather than the workflow itself.

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 is provided about when to use this tool versus related tools such as delete_workflow, undo_workflow_run, or list_workflow_runs. The description offers no context, preconditions, or use-case clarification.

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