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

The annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so 'Read-only: the rules cannot be changed from here' largely restates structured data rather than adding to it. What the description does contribute beyond annotations is the reported content of each rule, including last-run status and changed-object counts, but it says nothing about volume, pagination, ordering, or permissions needed to see rules.

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?

Everything is delivered in a single front-loaded sentence of the form verb + resource + returned fields, followed by a short scope caveat; no sentence is filler. It is dense with commas but readable, and the important action is in the first three words.

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?

With no output schema and no parameters, the description carries the burden of describing return values and does so thoroughly — name, description, enabled state, ad type, level, marketplaces, schedule, next run and last-run outcome. For completeness it would still help to know whether results are paginated or how long rule lists typically run, but nothing critical to invocation is missing.

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 takes zero parameters, so there is no parameter meaning to convey and the schema leaves nothing ambiguous. The description correctly avoids inventing inputs and spends its space on what the caller cannot otherwise infer.

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 definition opens with a specific verb and resource ('List the account's automation rules') and then enumerates exactly which fields come back, so the agent knows the shape of the result. It stops short of distinguishing itself from the sibling list_rule_runs, which covers run history and could easily be confused with the 'how the last run went' clause here.

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 explicit when-to-use guidance and no routing to alternatives: the definition never says to call list_rule_runs for detailed per-run history or to use another family of tools for rule-adjacent data. The only usage-adjacent signal is 'the rules cannot be changed from here', which tells the agent what it cannot do but not when this tool is the right choice.

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