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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful context by enumerating what the revision contains (body, sources, conditions, content hash, review state, attached outcome reports), but omits behavior on a missing/invalid revision_id and any authorization or rate-limit details.

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 that leads with the action and then enumerates the payload. Efficient with no filler, though the long comma-separated list slightly dilutes scannability.

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 no output schema, the enumeration of returned fields is valuable and largely closes the return-value gap. Still, the second parameter is unexplained and error cases for an unresolvable revision_id are unaddressed, leaving moderate gaps for a read 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 description coverage is 0%, so the description carries the full burden. It hints at attached outcome reports, touching on the include_unreviewed_reports concept, but never explains the boolean's include/exclude semantics, and says nothing about the revision_id format beyond the schema's regex.

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 precise verb and resource ('Read one exact revision of a Noosphere record in full') and enumerates the returned content. Combined with the title 'Read one exact revision', an agent can clearly separate this from sibling listing/search tools like search or write tools like propose_revision.

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?

Usage is implied by the required revision_id: retrieve a specific revision when you have its id. However, the description never says when to prefer this over search or how it relates to annotate/report_outcome, and gives no exclusions or prerequisites.

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