fetch_rule_readme_documentaion

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation by saying 'Retrieve' and detailing the return fields, but it does not disclose potential errors, permissions required, or any side effects.

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 well-structured with Args and Returns sections, but could be slightly more concise. The opening sentence is clear, and the details are appropriately placed without extraneous information.

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 low complexity (1 parameter) and presence of an output schema, the description adequately covers purpose, parameter semantics, and return fields. It does not need to explain return values in depth since the output schema exists.

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 description adds meaning beyond the input schema: it explains the 'name' parameter as 'The exact name of the rule to retrieve README for'. Given 0% schema coverage, this fully compensates for the missing schema documentation.

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 verb 'Retrieve' and resource 'README documentation for a specific rule by name'. It distinguishes from sibling tools like create_rule_readme, update_rule_readme, and fetch_rule_design_notes by specifying this is for documentation reading only.

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 notes this is useful 'for understanding how to properly use a rule in workflows', providing a clear use case. However, it does not explicitly mention when not to use it or contrast with alternatives like create_rule_readme.

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