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

Given that readOnlyHint=true and destructiveHint=false already cover the safety profile, the description adds meaningful behavioral context: rules are evaluated in order on every wake, each rule pairs a trigger with an action, and the hash is the published commitment. It does not contradict the read-only annotation. It stops short of describing the response format, but the annotation already covers the key safety expectation.

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 three sentences and every sentence contributes substantive context about the rule list, provenance, and hash. It is not bloated, though the phrasing 'and whether it is the one you wrote or the list a hosted agent starts with' is slightly dense and indirect for a simple read operation.

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 tool with no output schema, the description is responsible for conveying what the call returns. It discusses the rule list, per-rule structure, and hash, but it never explicitly states that the tool returns the current rule list and its hash. An agent could infer this from the title, but the description itself is suggestive rather than explicit.

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 and schema description coverage is 100%, so the schema imposes no hidden burdens. The description does not need to document parameter semantics because there are no parameters; the baseline of 4 for a zero-parameter tool applies.

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 tool name and title clearly supply the verb 'read' and the resource 'your own policy / rule list', and the description opens with 'Your own policy: the rule list evaluated in order on every wake.' This distinguishes it from siblings like read_facts or read_skills. However, the description defines the rules more than it explicitly states the read operation itself, so it is clear but not maximally direct.

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 useful context about why rules matter and what the hash represents, but it never explicitly says when an agent should call read_my_rules versus an alternative. It acknowledges that 'changing these rules visibly changes what you are committed to' without naming set_my_rules as the mutation counterpart, leaving the usage decision mostly implied.

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