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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered without the description. The description adds only 'recent' and 'active client' scoping, leaving undefined what 'recent' means, whether results are paginated, and why write-flavored parameters (confirm, dry_run, confirm_live) appear in a read-only list call.

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 tight sentence with the resource front-loaded and no filler. It is efficient, though arguably under-specified rather than genuinely concise for a 33-parameter tool.

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, but for a 33-parameter tool with zero required fields and zero schema coverage the description is far too thin. It leaves the agent unable to determine which of the many filters (date ranges, rule_id, action_id, thresholds, etc.) actually apply.

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 33 parameters with 0% description coverage and no enums, and the description mentions none of them. It gives no indication which parameters are meaningful for listing versus the shared/irrelevant blob, so the agent has no basis for filtering correctly.

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 (pause proposals and executions) scoped to the active client, so the agent can distinguish it from sibling list tools like automate_list_automation_rules. Minor inconsistency: the title promises 'pause and budget proposals' while the description only mentions pause proposals and executions.

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?

No guidance on when to use this versus the many sibling listing tools (automate_list_automation_rules, automate_list_alert_rules, automate_list_seo_alert_rules), and no prerequisites or exclusions. 'For the active client' implies context but does not say how the client is determined or when the tool is appropriate.

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