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

Annotations already declare destructiveHint and idempotentHint, but the description adds real value: it spells out the concrete consequence of the deletion ('no longer runs on future triggers') and the retry semantics ('a repeat call with the same idempotency_key returns the original result'). It omits permission requirements and error behavior when the id is absent.

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 action, with no redundant or filler content. Each sentence contributes a distinct fact (action, consequence, idempotency).

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 already covering safety and idempotency, and no output schema, the description supplies the key missing behavioral context. Only auth/permission needs and not-found handling remain unaddressed.

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 coverage is only 40%, so the description must compensate. It explains the two required parameters well — 'by id' and the idempotency_key retry behavior — but says nothing about the optional brand_id, workspace_id, or query parameters.

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 a content automation rule by id'), making the operation unambiguous. It does not explicitly distinguish itself from the sibling delete_inbox_automation, but the resource naming inherently separates them.

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?

The description implies usage by explaining the effect ('no longer runs on future triggers'), but it never states when to delete versus disabling via update_content_automation, nor names any alternative. Guidance is inferable rather than explicit.

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