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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is partially covered. The description adds real context beyond that: already-sent messages are unaffected, which is the key question an agent faces before deleting a live automation. It does not state behavior on a missing/invalid id or whether the delete is reversible, so it falls short of 5.

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 short sentences, front-loaded with the destructive action and its effect, then the alternative. No filler or repetition of structured fields.

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?

No output schema is needed for a delete, and annotations cover the destructive profile. The description covers effect and the delete-vs-pause decision, but says nothing about failure modes (e.g., unknown id) or confirmation requirements.

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?

One parameter at 0% schema description coverage, so the description carries the burden and does not mention automation_id at all. The name is self-explanatory as a UUID identifier, which keeps it at the minimum-viable baseline rather than lower.

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') and immediately names the outcome ('so it stops sending'), which separates it from pause-oriented siblings. An agent can distinguish it from update_automation without opening either schema.

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?

Gives an explicit when-not and a named alternative: to pause temporarily, use update_automation with enabled: false. The selection rule between delete and pause is fully spelled out.

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