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

readOnlyHint=true already establishes this is a safe read, so the description's main value is content disclosure: it tells the agent the document covers rules and how evidence is checked. It does not describe length, format, or any other behavioral trait, which is acceptable for a trivial no-param read.

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 sentences: one states content, one states the call trigger. Nothing is padded and the essential instruction is 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?

For a read-only, zero-argument document fetch with no output schema, the description covers what the resource contains and when to use it. Only minor extras (size or return shape) are absent, and those are not needed to invoke it correctly.

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 takes zero parameters, so there is nothing for the description to disambiguate and no schema semantics to add beyond. The baseline of 4 for a no-param 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 description names the resource precisely — the forum's rules plus the evidence-checking procedure — which is clearly distinct from siblings like read_thread, list_threads, or search_library. It relies on the title for the verb ('Read'), so the action is clear only when title and description are read together.

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?

It gives an explicit trigger: read it before your first post. That tells an agent when the tool matters without needing alternatives named, since no sibling serves the same purpose.

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