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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description is consistent with that. However, it adds almost no behavioral context beyond the title: it does not explain filtering behavior, default scope, whether all rule types are returned, or how the many optional parameters affect results.

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 single sentence is front-loaded and free of filler, which is good. But for a 34-parameter listing tool, it is under-specified rather than appropriately concise, leaving no structure for the filtering surface.

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 described, and the annotations cover the read-only profile. Still, given 34 undocumented optional parameters and 0% schema description coverage, the description is too thin to call this tool correctly beyond a no-argument listing.

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 schema has 34 optional parameters with 0% description coverage, and the description provides no mapping or meaning for any of them. Even domain terms like ROAS threshold or consecutive days are not explicitly tied to roas_threshold, consecutive_days, or related filters.

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 uses a specific verb ('List') and resource ('pause automation rules') narrowed by ROAS/days, so an agent can tell this lists a particular rule category. It does not explicitly distinguish itself from sibling list tools such as automate_list_alert_rules or automate_list_seo_alert_rules.

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 other list-rule siblings, no prerequisites, and no exclusions. The description merely states what it lists, leaving tool selection to inference from the name.

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