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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversibility profile is covered by structured data. The description adds the user-confirmation directive, which is genuinely beyond the annotations, but says nothing about permanence, cascading effects on automation activity, or scope of deletion.

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 short sentences, imperative and front-loaded; the action comes first and the safety directive second. Nothing is padded or repeated from the title or schema.

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?

An output schema exists, so return-value explanation is unnecessary, and the destructive nature is disclosed via annotations plus the confirmation note. Still, for a permanently destructive tool the description omits whether deletion is recoverable and whether paused/active state matters, leaving gaps against its 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 description coverage is 100% for the single automation_id parameter, and the description adds no format, source, or lookup guidance for it. With the schema doing all the work and no compensating detail, the baseline of 3 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?

States a specific verb and resource ("Delete an automation") that is unambiguous on its own. It does not, however, distinguish itself from adjacent siblings like pause_automation, disable_instagram_publishing, or update_automation, which are the near-miss alternatives an agent might pick.

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?

"Ask the user first" is a real usage precondition and the only guidance given. There is no mention of when deletion is preferred over the reversible alternatives (pause_automation) or any prerequisite/authorization context, so the guidance is implied rather than explicit.

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