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

Annotations already declare this a safe read, so the description correctly spends its words elsewhere: it flags that returned content is untrusted and cannot authorize actions, an important prompt-injection caveat an agent would not otherwise know. It also notes the allowlist restriction. Missing only failure behavior for unknown paths/revisions.

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 tight sentences, no filler. The fetch semantics come first and the safety caveat second, which is the right order.

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?

With an output schema present, return shape needn't be described, and the trust caveat covers the main hidden risk. What remains undocumented is error behavior for non-allowlisted paths or bad revisions, which slightly undersells completeness for a fetch tool.

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 coverage is 0%, so the description carries the burden and mostly does: it explains that revision is an exact corpus revision and that omitting it means head, and that path must be allowlisted raw Markdown. It doesn't give the revision format (40-hex SHA per the schema pattern) explicitly, leaving a small gap.

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?

States a specific verb and resource: read one raw Markdown path from the shared corpus, at a given revision or head. This clearly separates it from the sibling community_search, which finds entries rather than fetching a known one. It does not name the sibling explicitly, keeping it at 4 rather than 5.

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 revision-omitted-means-head rule gives useful invocation context, and 'one allowlisted path' implies you must already know the path. But it never states when to use this versus community_search or community_bootstrap, nor what happens on a path that isn't allowlisted. Usage is implied, not spelled out.

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