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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one behavioral nuance — that job/department filters surface inherited pipeline rules and pipeline filters surface hiring-step rules — which shapes what the caller actually receives. It says nothing about pagination, result cap, or ordering, so it is adequate but not rich.

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 sentences, both front-loaded with the operation then the filter semantics. There is no filler, repetition of the title, or restatement of schema types — every clause adds information.

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?

There is no output schema, so the description is the only source of shape information, and it covers what entities are returned and how inheritance expands results. It omits pagination/limits and default ordering, which an agent listing potentially large rule sets would want, but the essentials for a read-only list call are present.

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%, so the description carries the full burden, and it documents 6 of 7 parameters (job_id, department_id, pipeline_id, trigger, email, is_active) with semantic detail such as job_id being null for pipeline rules. Only request_id is left unexplained, which is a minor gap but prevents a perfect score.

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 and resource ('List all job and pipeline rules') and clarifies the scope is both job- and pipeline-level rules. This distinguishes it from yardstick_automation_rules_read (single rule), but it does not explicitly name any sibling or contrast the list/read pair, 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 description gives real filtering context ('job_id null for pipeline rules', which filters include inherited pipeline rules and hiring-step rules), which is useful for choosing the right query. However, it never states when to use this tool versus automation_rules_read or automation_runs_list, and there are no prerequisites or exclusions.

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