Delete Workflow

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds 'permanently,' which reinforces irreversibility, but does not disclose side effects on related resources or error behavior. This is adequate given annotation coverage but not enriched.

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, focused sentence with no filler or repetition. It conveys the essential action and scope with zero wasted 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?

For a simple single-resource deletion with one parameter, no output schema, and comprehensive annotations, the description is sufficient. It could mention return behavior or edge cases, but those are not critical given the tool's simplicity.

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 schema fully documents flow_id with a description, and the description's 'by id' merely restates that. No additional parameter semantics are provided, so the baseline score of 3 for high schema coverage 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?

The description 'Permanently delete a workflow by id' uses a specific verb (delete), identifies the resource (workflow), and clarifies it is a single deletion by ID. It clearly distinguishes from sibling tools like bulk delete or update.

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 usage is implied: this tool deletes a single workflow, while bulk deletion is handled by lyzr_bulk_delete_workflows. However, the description does not explicitly mention alternatives or exclusions, leaving the agent to infer the intended scope from context.

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