Remove Automation

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

Discloses key behavioral traits: removal is irreversible and stops future runs. Since no annotations are provided, the description carries the full burden, but it does not cover all possible side effects.

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 sentences: purpose followed by two usage guidelines. Every sentence adds value with no redundancy. Front-loaded with the core action.

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?

Given no output schema and a simple single-parameter tool, the description covers purpose, parameter, and critical usage guidance. Minor gap: no mention of what the response indicates (e.g., success confirmation).

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 single parameter 'id' has a description in the schema that matches the description text exactly. With 100% schema coverage, the description adds no extra meaning, so baseline 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?

The description clearly states the verb 'Remove' and the resource 'automation', and specifies identification by ID or dashboard URL. It distinguishes from sibling tools like 'create-automation' or 'update-automation'.

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 instructs to double-check with user, reference automation name, warn of irreversible removal, and only use after explicit confirmation. This provides precise when-to-use guidance.

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