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

Annotations already mark the call as read-only, idempotent, and non-destructive; the description adds a useful behavioral model by explaining rules are inert config and that authoring does not fire side effects while an executor child runs rules later. This goes beyond the structured hints without contradicting them.

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?

Two short sentences, front-loaded with the primary action and followed by the one behavioral clarification that matters. No redundant prose or repetition of the title.

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 annotated list call, the description is nearly complete: it covers what is listed, at what scope, and the side-effect model. There is no output schema, so the return shape is left implicit, and pagination/filtering is not mentioned, but the single optional parameter and read-only annotations make these minor gaps.

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% and the description does not explain the sole request_id parameter, so no extra meaning is added beyond the raw schema. The impact is modest because request_id is optional and self-describing as a request identifier, but the low-coverage rule is not satisfied.

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 names a specific verb and resource ('List ... stage automation rules') and scopes it to the organization, so an agent can tell that this enumerates rules rather than reading, creating, or previewing them. It does not explicitly contrast with sibling automation-rule tools, so it stops short of the strongest sibling differentiation.

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?

The inert-config clause implies this is the safe inspection path and that execution happens later through an executor child, but it never states when to choose this tool over automation_rules_read, preview, or runs_list. The usage guidance is therefore implied rather than explicit.

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