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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral context beyond that: the result is ordered and curated, and it is meant to be consumed before per-rule calls. It does not describe size/pagination of the returned sequence, but with an output schema present that burden is light.

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?

Front-loaded with the purpose and the proactive-usage cue, and the ordering guidance is compact. However, the twelve-item workflow list is duplicated from the enum, which is wasted space an agent can already read from the schema.

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 single-enum, read-only retrieval tool with an output schema, the description supplies everything needed: what it returns, when to call it, and how it fits into the get_rule/check_rule pipeline. Return-value details are correctly left to the output schema.

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 coverage is 100% and the enum already enumerates all twelve slugs. The description merely repeats the same list verbatim, adding no extra meaning about constraints or how to choose a workflow slug — the baseline of 3 applies when the schema does the work.

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 ('Returns a curated, ordered sequence of rules for a specific checklist workflow') and clarifies the unit of work (a named workflow, not an individual rule). It also distinguishes itself from siblings by positioning itself as the entry point before get_rule and check_rule.

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?

Explicitly says 'Use PROACTIVELY when performing comprehensive audits or setting up new projects' and gives a concrete ordering: this tool FIRST, then get_rule per step, then check_rule to validate. The condition and the alternatives are both named.

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