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

Annotations already declare destructiveHint=true, so the danger is known. The description adds real value beyond them by naming what is destroyed (activity log), what is preserved (already-sent DMs stay sent), and requiring user confirmation. That is genuine disclosure of consequences, but it stops short of stating irreversibility, permission requirements, or the response shape.

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, each carrying a distinct fact: scope/effect, the safer alternative, the confirmation requirement. Front-loaded with the action and with zero padding.

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 one-parameter destructive tool, annotations cover the safety profile and the description covers consequences, the alternative path, and the pre-call safeguard. No output schema is needed for a delete, so nothing an agent requires is missing.

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?

A single parameter at 100% schema coverage, with the schema itself documenting that the id comes from list_automations. The description adds no format or sourcing detail beyond that, so the baseline 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?

Specific verb (delete) plus the exact resource (comment-to-DM automation), the supported platforms, and the collateral (activity log). It also implicitly separates itself from update_automation and list_automations by naming the latter as the id source.

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 routes the agent to update_automation with status 'paused' when the intent is only temporary, and adds a 'confirm with the user first' precondition. When-to-use-not and the alternative are both stated, not inferred.

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