List Global Rules

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

Annotations already declare readOnlyHint, destructiveHint false, and idempotentHint true. The description adds behavioral context beyond annotations: the exact location (~/.claude/rules/), the fixed number of 17 rules, and enumerates them by name. No contradictions. Slight deduction because the list format is implicit.

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 concise sentences plus a bullet-like list. The first sentence states the core function and location; the second provides usage guidance. Every element is essential; no redundancy. Well-structured and 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?

Given zero parameters and no output schema, the description fully covers what the agent needs: it lists the exact rules, explains the path, and directs to the parent tool for reading. It is complete for this simple listing task.

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?

The tool has zero parameters, which yields a baseline of 4 per guidelines. The description does not need to add parameter meaning since there are none. No additional parameter information is required.

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 explicitly states 'Lists all 17 global rule names' with the specific path and provides the full list, leaving no ambiguity about the resource and scope. It is clearly distinguished from sibling tools like rules_get_global_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?

The description includes explicit guidance: 'Use rules_get_global_rule to read a specific rule.' This tells the agent when to use the sibling tool instead. While it could also state when not to use this tool, the guidance is clear and practical.

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