delete_automation

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

Annotations include destructiveHint=true, and the description's 'Delete' aligns with that. The description adds the permission requirement (allow_automations), providing extra context beyond annotations. However, it does not disclose other potential behavioral traits like irreversibility or cascading effects on related runs.

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 two short, front-loaded sentences: 'Delete a scheduled automation.' and 'Requires allow_automations.' Every word is purposeful, with no wasted text.

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 one-parameter destructive tool, the description plus annotations (destructiveHint=true) cover the essentials: what it does and a key prerequisite. It could add details about permanence or effects on associated runs, but the tool's simplicity and context make it adequately complete.

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 description does not explicitly explain the 'id' parameter, but the phrase 'Delete a scheduled automation' implies the id refers to the automation to be deleted. With schema description coverage at 0%, the description provides minimal parameter guidance, though the single parameter's meaning is easily inferred.

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 'Delete a scheduled automation' uses a specific verb and resource, clearly distinguishing it from sibling tools like create_automation, update_automation, and list_automations.

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 provides a prerequisite ('Requires allow_automations') but does not explicitly discuss when to use this tool versus alternatives, such as using update_automation to disable instead. The intended use is clear from the name and description, but no explicit when/when-not guidance is given.

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