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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no further behavioral context - nothing about pagination, filter behavior, defaults, or that the 33 parameters are all optional filters, leaving the description essentially empty of value beyond the annotation.

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?

It is a single short, front-loaded sentence with no wasted words, but it is under-specified rather than genuinely concise, and the 'N-days' shorthand is cryptic rather than clarifying.

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?

An output schema exists, so return values need not be explained, but for a read-only list tool with 33 undocumented optional filters and no usage guidance, the description is far too thin to let an agent call it correctly.

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?

The tool exposes 33 parameters at 0% schema description coverage, and the description says nothing about any of them. Only a loose hint ('ROAS-below-N-days' gesturing at roas_threshold/consecutive_days) exists, which does not compensate for the near-total absence of parameter meaning.

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 states a specific verb (List) and resource (automation rules) qualified by 'ROAS-below-N-days pause', which distinguishes it from siblings like automate_list_alert_rules and automate_list_seo_alert_rules. It does not, however, explicitly contrast itself with those list siblings, so it falls just short of a 5.

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 alternatives such as automate_list_actions or the SEO/alert list siblings, and no prerequisites or exclusions are stated. The agent must infer usage entirely from the name and title.

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