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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' is largely redundant. The description does add genuinely new behavior: result ordering (newest first) and the 100-item page cap, which an agent needs to page correctly.

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?

A single dense sentence with the scope, ordering, page cap, paging instruction and safety profile front-loaded in that order. No filler and nothing repeated.

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 no-required-param list tool with annotations covering the safety profile, the description covers scope, ordering and pagination adequately. Since no output schema exists, it could say a bit more about what a rule entry looks like, but nothing needed to invoke it correctly is missing.

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 67%; the `path` property carries no schema description, and the description compensates by clarifying it is a workspace-relative path. The offset/paging semantics are already in the schema, and the description restates the page-size tie-in usefully.

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?

Specific verb (List) plus resource (rules) scoped to a workspace-relative path, and the word 'rules' inherently distinguishes it from the list_memories/list_skills siblings. It stops short of explicitly naming those alternatives, so an agent must infer the split from the resource noun alone.

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?

Usage is implied by the scoping (list rules under a path) and it gives a concrete paging recipe ('pass offset for the next page'), but there is no explicit when-to-use/when-not guidance and no mention of the sibling list tools that fetch memories or skills instead.

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