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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is known; the description adds real value by framing the blast radius (live email-sending system) and disclosing that the response returns a full redacted rule snapshot for recreation. It stops short of describing downstream effects such as in-flight or queued sends, which would complete the picture for a deletion tool.

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, front-loaded with the destructive action, then the safer alternative, then the recovery affordance. No filler or restated title language.

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 two-parameter destructive tool with no output schema, the definition covers action, risk framing, alternative path, usage gate, and return payload. An agent has everything needed to decide whether to call it and what to expect back.

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 0% and both parameters are bare UUIDs with only format/pattern validation, so the description must carry the meaning. It implies that webinarId identifies a tenant-owned webinar and automationId identifies the rule, but never states that the rule must belong to that webinar or what happens on a mismatch. This is partial compensation rather than full.

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 opens with a specific verb and resource: "Permanently remove an automation rule from a tenant-owned webinar." The word "permanently" and the tenant scoping distinguish it clearly from sibling operations such as automations_update or automations_list.

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?

It names the explicit alternative and condition: call automations_update with enabled:false to temporarily disable a rule without losing config. It also adds a positive gate ("Use this tool only when permanent removal is intended"), giving both when-to-use and when-not-to-use guidance.

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