Get Global Rule

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds the file path and return content, but does not offer significant behavioral context beyond what annotations provide. It is consistent and adds marginal value.

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 description is structured as a docstring with Args and Returns sections, making it easy to parse. It is concise but includes necessary details like the list of valid values. Could be slightly tighter but is well-organized.

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 the single parameter with full schema coverage, rich annotations, and no output schema, the description covers what the tool does, input format, valid values, and return type. It is complete for the tool's simplicity, though error handling is not mentioned.

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 100%, and the description expands on it by listing valid values and clarifying the naming convention (e.g., '.md' suffix omitted). It adds meaning beyond the schema by giving explicit examples and the path format.

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 clearly states the action 'Reads a specific global rule file by name from ~/.claude/rules/{name}.md', specifying the verb (reads), resource (global rule file), and location. It effectively distinguishes from sibling tools like rules_list_global_rules and rules_get_global.

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 a comprehensive list of valid rule names, guiding correct input. It implicitly defines when to use this tool (when needing content of a specific rule) but does not explicitly state when not to use it or suggest alternatives like listing rules first. However, the list and context are helpful.

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