delete_automation

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

Discloses that deleting an automation also deletes its runs ('its runs cascade with it'). No annotations present, so description carries full burden; it adequately reveals this cascading behavior.

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 sentences, each serving a distinct purpose: main action with cascading effect, and usage condition. No extraneous 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?

Fully describes the core operation and constraints. No output schema exists, so no need to explain return values. Could mention error cases or permissions, but current content is sufficient given tool complexity.

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% (both id and sender described). Description does not add additional meaning beyond what schema provides, so baseline score of 3 is appropriate.

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 the action 'Delete an automation by id' with a specific resource (automation). Differentiates from sibling tools like pause_automation by clarifying that runs cascade.

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?

Explicitly states the condition 'Only while draft or paused' and instructs to 'pause it first.' Provides clear context for when to use, but does not explicitly contrast with alternatives.

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