Delete workflow

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

Annotations already cover the safety profile (destructiveHint=true, readOnlyHint=false, openWorldHint=true, idempotentHint=false). The description adds genuinely new context beyond those: provider scopes, locks and credits apply, and the mandatory confirmation / one-submission-only behavior. It stops short of describing what is destroyed or return behavior.

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?

Three tight clauses with the operation front-loaded first. The 'Current Bannerbear V5 operation' phrasing is mildly filler, but nothing else is wasted and the key constraints follow immediately.

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 destructive single-parameter deletion with no output schema, the description covers confirmation, credit/lock implications, and single-submission behavior. It omits what the deletion does to dependent workflow runs, but the destructive annotation carries much of that burden.

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 description coverage is 67%; uid has no prose description (only pattern/length constraints) while account and confirm are documented. The description's 'mandatory confirmation' clause echoes the confirm parameter but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 via the endpoint 'DELETE /v5/workflows/{uid}', which clearly identifies it as deleting a workflow. Among many delete siblings (delete_image_template, delete_webhook, delete_instant_url, delete_animation_template), the resource name differentiates it implicitly, though no sibling is called out by name.

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 states a confirmation requirement ('Mandatory confirmation before provider execution') and a constraint ('one submission only'), but gives no guidance on when to choose this tool over alternatives or any explicit when-not condition. Usage context is left to inference.

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