delete_workflow

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds edition/license/permission gating and 404 behavior, which is genuine extra context. It does not say what is destroyed beyond the workflow itself (runs, schedules, history) or whether deletion is recoverable, and the "empty lists" remark is unclear for a DELETE operation.

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 tight sentences with the action front-loaded. The edition/permission caveat earns its place; the "empty lists" clause is somewhat noisy and confusing in a delete context but is the only padding.

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 mutation with no output schema, the description covers availability gating but omits scope of deletion (cascading effects on workflow runs or schedules) and any indication of the response. Annotations supply the safety flags, so the remaining gap is moderate rather than severe.

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 0% for two required integer params, so the description carries the burden. The embedded path template DELETE /project/{project_id}/workflows/{workflow_id} does clarify the role and ordering of each identifier, which is real value. It adds no constraints beyond that, such as whether IDs must belong to the same project.

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 ("Remove workflow") and reinforces it with the DELETE endpoint. An agent can distinguish it from update_workflow/create_workflow without effort. It does not, however, differentiate itself from the many other delete_* siblings beyond the noun, which is probably sufficient here.

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 gives availability caveats (edition, license, permissions) and warns that some Community routes return 404 or empty lists, which is useful context for interpreting failures. But it never says when to use this versus alternatives, nor states prerequisites or side effects that would guide selection. Usage is only implied by the verb.

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