kaiten_delete_automation

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

No annotations are present, so the description carries the full behavioral burden, but it only restates the delete action. It does not disclose whether deletion is permanent/irreversible, whether active automation triggers are affected, or what the success/failure response looks like — material gaps for a destructive 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?

A single eight-word sentence conveys the full operation with zero wasted words, and the action is front-loaded at the very start.

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?

Complete on the parameter side — both required params are documented and simple, and no output schema is expected for a delete. However, with no annotations and no output schema, a note that deletion is permanent and an indication of the success response would meaningfully improve completeness for a destructive tool.

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 100% and both parameters are adequately described ('Space ID' and 'Automation ID (UUID)'), so the schema carries the semantic weight. The description adds no parameter detail, which is acceptable at this coverage level.

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 ('delete') with a precise resource ('automation') and scope ('from a Kaiten space'), leaving no ambiguity about what the tool does. It distinguishes clearly from sibling tools like kaiten_delete_workflow and kaiten_delete_board, and from the automation-focused siblings (list/create/get/update/copy).

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 when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives such as kaiten_update_automation for modifying an automation or kaiten_copy_automation for duplicating one, nor any prerequisites like the automation needing to exist in the space.

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