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

The description adds no behavioral context beyond the operation's effect, which is already implied by the verb 'Delete' and confirmed by the annotations ('destructiveHint': true). It fails to clarify potential side effects of the deletion.

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?

The description is extremely concise and efficient, serving only as a minimal identifier, making it appropriate for its brief function.

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?

Given the extreme complexity of 34 parameters with 0% schema coverage, the description is functionally incomplete. It gives the AI agent no meaningful context to guide its parameter filling or decision-making before execution.

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?

With 34 input parameters and 0% schema description coverage, the description provides no semantic value to the parameters. An agent cannot use this single sentence to understand how or why specific parameters (like 'roas_threshold' or 'lookback_days') are relevant.

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 clearly states the action ('Delete') and the resource ('automation rule'). However, it fails to distinguish this tool from other deletion siblings (like delete_alert_rule), which requires relying heavily on the title.

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 only provides a single operational prerequisite ('Admin only'). It offers no guidance on when to use this tool versus when to use related list or upsert functions, nor does it define any failure conditions.

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