delete_workflow

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

With no annotations, the description effectively discloses key behaviors: SKU-dependent effects (deletes entire app vs. specific workflow) and irreversibility. It adds context beyond basic deletion, though it could mention permission requirements.

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 clear, front-loaded sentences efficiently convey purpose, SKU difference, and caution, with no unnecessary information.

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 description covers behavioral differences and irreversibility but lacks details on return values, error handling, or permission requirements. Given no output schema and no annotations, some completeness gaps remain.

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%, but the description adds value by explaining that workflowName is required for Standard SKU and providing SKU context. This enhances parameter understanding beyond the schema descriptions.

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 'Delete a workflow' and differentiates between Consumption (deletes entire Logic App) and Standard (deletes specific workflow), making the tool's purpose highly specific and distinct from siblings like disable_workflow.

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 warns 'Use with caution as this action cannot be undone,' implying careful usage, but does not provide explicit guidance on when to use this tool versus alternatives like disable_workflow or other deletion methods.

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