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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description's one genuine addition is the caveat that the result is "never authorisation" — useful behavioral framing that prevents misuse. It does not describe output shape or whether the optional action changes the response.

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 short, front-loaded sentences with no filler; the key constraint ("never authorisation") is stated early. It borders on under-specified rather than bloated, but nothing is wasted.

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 single-optional-param read tool with annotations covering safety and no output schema, the description is minimally sufficient. It leaves the scope of "rules" (whose rules, about what domain) undefined, which matters given many similarly named get_* siblings, but it does communicate the essential non-authoritative stance.

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 optional action parameter already lists example values (publish_claim, submit_check, read_public, vouch). The description adds nothing about what passing an action does versus omitting it, so it neither extends nor compensates. Baseline 3 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 description states a resource ("Public structured rules") and a secondary function ("a conservative action check"), so the agent can infer it returns rules and can validate a planned action. However, "conservative action check" is opaque jargon, and it does not distinguish itself from near-siblings like get_arena_instructions, get_calibration, or get_precedents, which all read as rule-like lookups.

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 title supplies the when-to-use cue ("Read rules before acting") and the description frames it as "decision support" rather than an authoritative source. But no alternatives are named for when the action check vs. the plain rules listing is appropriate, and there is no explicit when-not-to-use. Guidance is implied rather than stated.

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