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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false, covering the safety profile. The description adds nothing on top of that: no cascade behavior, no statement about whether the action must be inactive first, no confirmation or permission requirements, no recovery implications.

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?

A single three-word sentence with zero waste and the essential verb front-loaded. However, this brevity stems from under-specification rather than efficient communication, so it cannot be rewarded as genuinely well-structured.

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 destructive mutation with annotations covering reversibility and idempotency, the description still omits important operational context: what happens to related records when an action is deleted, and whether dependent automations or campaigns are affected. It is not misleading, but it is materially incomplete.

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%, with both actionId and apiKey documented in the schema itself, so the baseline of 3 applies. The description contributes no additional parameter meaning, but the schema already carries the full burden.

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?

"Delete an Action" only restates the tool name and title; it adds no scope, target detail, or distinction beyond the verb+resource already conveyed by the identifier. It is a tautology rather than a genuine statement of purpose, though the verb+resource pairing does at least identify what entity is affected.

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?

There is no guidance on when to use this tool versus the many siblings (delete_audience, delete_campaign, delete_contact, delete_topic, delete_webhook, update_action, get_action). No prerequisites such as state requirements or ordering relative to other operations are mentioned.

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