workflow_delete

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

With no annotations provided, the description carries full burden but only states it deletes a workflow. It lacks critical behavioral details: whether deletion is permanent/reversible, permission requirements, side effects (e.g., related data removal), or error conditions (e.g., invalid ID handling).

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 front-loaded with the core action ('Delete a workflow') and uses a structured Args/Returns format efficiently. However, the Returns statement is vague ('Confirmation of deletion') and could be more precise without adding bulk.

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 tool with 1 parameter, no annotations, and an output schema (which should cover return values), the description is minimally adequate. It states the action and parameter but misses behavioral context (e.g., irreversibility) and usage guidance, leaving gaps for safe agent operation.

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%, but the description adds minimal semantics by naming 'workflow_id' and stating it's 'The workflow ID to delete'. This clarifies the parameter's role beyond the schema's title 'Workflow Id', though it doesn't specify format or sourcing (e.g., from workflows_list).

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 verb 'Delete' and resource 'workflow', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'workflow_update' or 'workflow_get' beyond the obvious action difference, which prevents a perfect score.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing workflow_id from workflows_list), exclusions (e.g., cannot delete active workflows), or comparisons with siblings like workflow_update for modifications.

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