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

With no annotations provided, the description carries the full safety-profile burden. It does add useful context by disclosing the returned metadata (name, trigger type, enabled status, linked pipeline) and the tenant scoping, but says nothing about pagination, result limits, or permission requirements.

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 tight sentences with no filler: the first gives purpose plus scope, the second enumerates the return shape. The most important information (what it lists and for whom) is front-loaded.

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?

Although there is no output schema, the description compensates by naming the returned fields, and all three simple parameters are documented in the schema. For a read-only list tool this is nearly complete; only pagination and permission behavior are unaddressed.

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 100%, so all three parameters (enabled, tenant_id, trigger_type) are already documented, including the auto-injection of tenant_id. The description only summarizes them as 'optional filters' and adds no per-parameter syntax or interaction detail, so the baseline of 3 applies.

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 (automation rules) scoped to 'the current tenant', which is clearly distinct from the pipeline/collection/model resources of its siblings. It does not explicitly reference or differentiate itself from any sibling tool, so it stops short of a 5.

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 mention of 'optional filters' hints that filters may be applied, but there is no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites stated. Usage must be inferred 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.