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 by structured data. The description adds nothing beyond that — it does not explain filtering behavior, pagination, or why a read-only listing tool exposes write-flavored parameters such as confirm, confirm_live, dry_run and action_id.

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 front-loaded sentence with zero wasted words. It is tight and readable, though its brevity borders on under-specification for a tool with this many parameters.

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. However, with 33 undocumented parameters, no usage guidance, and no filter semantics, the description falls well short of what an agent needs to invoke this tool correctly in the presence of several similarly named listing siblings.

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 0% across 33 parameters, so the description carries the full explanatory burden. The parenthetical '(ROAS/CPA/spend pace)' vaguely gestures at metric-related fields but gives no meaning to name, scope, threshold, operator, condition, lookback_days, or the confirm/dry_run pair.

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 ('List') and resource ('ads performance alert rules') and hints at the metric domain (ROAS/CPA/spend pace). The word 'ads' partially distinguishes it from the sibling automate_list_seo_alert_rules and automate_list_automation_rules, though the separation is by inference rather than explicit contrast.

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 when-to-use guidance, no prerequisites, and no mention of the other listing tools (automate_list_automation_rules, automate_list_seo_alert_rules) that an agent must choose between. The agent is left to infer selection entirely from the tool name.

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