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

The readOnlyHint annotation already signals this is a safe read operation. The description adds useful context that the rules are free and public, and that findings are not included here. It does not discuss pagination, result shape, or any access requirements, but for a simple list operation the annotation plus description is adequate.

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 first and last sentences are useful, but the middle sentence is garbled and repetitive: 'how many findings requires, what it applies to, and how severe a breach is' appears twice with broken phrasing. This redundancy undermines clarity and suggests an editing error, so the description is not cleanly concise.

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 zero-parameter, read-only list tool, the description is mostly complete: it identifies the resource and points to the findings endpoint for related data. However, there is no output schema and the description does not clarify the catalogue item structure or pagination behavior, leaving a small but real gap.

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?

This tool has zero parameters, so the baseline is 4. There are no parameter semantics to clarify, and the description appropriately focuses on behavior and scope rather than parameters.

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 opens with 'List the compliance rule catalogue,' which clearly identifies the action and resource. It also distinguishes this tool from the related findings tool by explicitly directing findings to `GET /v1/compliance/findings`.

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 provides clear usage context: this endpoint lists the public rules catalogue, while findings are located elsewhere via the findings endpoint. It could be more explicit by naming the sibling tool `list_compliance_findings`, but the separation between rules and findings is clearly conveyed.

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