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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds context beyond that by clarifying that paused rules include explanations and that some external-action rules cannot be managed through this interface. It does not describe ordering or pagination, but the annotations carry most of the safety profile.

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 description is a single front-loaded sentence with no wasted wording. It communicates the core action and the most important caveat immediately.

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?

For a simple read-only list tool with rich annotations and no meaningful parameters, the description is mostly complete: it states what is read and notes the website-managed exception. It does not describe return fields, but no output schema exists and the core invocation context is sufficiently covered.

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 only parameter is a required empty input object, so there are no meaningful parameter semantics to document. With effectively zero semantic parameters, a baseline of 4 is appropriate.

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 clear verb-resource pair: reading saved automation rules. It adds useful scope by mentioning paused explanations and external-action rules, though it does not explicitly distinguish this tool from sibling list tools such as list_approval_rules or list_vendor_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?

Usage is implied: call this to read saved automation rules. The note that external-action rules must be managed on the website provides a useful constraint, but there is no explicit when-to-use versus alternatives guidance or named sibling tool comparison.

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