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

No annotations are provided, so the description carries the full behavioral burden. It does not confirm this is a harmless read, state any auth or rate-limit constraints, or explain whether calling it with or without 'kind' changes what is returned. Only the returned content categories are disclosed.

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?

A single front-loaded sentence with no filler; each listed item maps to a plausible guidance section. Slightly list-heavy, and it omits the parameter that would resolve ambiguity, but it is efficiently sized.

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 tool with no output schema and one fully undocumented enum parameter, the description leaves the agent unable to decide which 'kind' to request or what each returns. The content enumeration is helpful but not sufficient to call the tool 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?

Schema description coverage is 0% and the sole parameter 'kind' (enum: leak, confession) is documented nowhere. The description does not mention the parameter at all, so it fails to compensate for the coverage gap even though the enum values hint at two guidance tracks.

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 verb is 'read' and the resource is guidance content, enumerated as qualification rules, inclusion pitfalls, stages/release choices, and proof-of-work difficulty. However, it is not distinguished from the several other read-oriented siblings (read_feed, read_own, get_reputation), and the description reads more like a table of contents than a purpose statement.

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?

There is no statement of when to call this versus alternatives such as check_status, get_challenge, or read_feed. The 'kind' enum suggests two distinct guidance contexts (leak vs confession), but the description never explains how usage differs between them or why an agent would pick one.

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