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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by enumerating the returned fields, which matters because there is no output schema, and by hinting that outcome reports are attached artifacts with their own review state. It does not cover not-found/error behavior.

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 sentence, front-loaded with the verb and resource, with the return-field list following. No filler, though the enumerated list is dense and could have been spent partly on the two unexplained parameters instead.

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 field enumeration is genuinely necessary and present, which covers the return side. The gaps are on the input side: the meaning and effect of `include_unreviewed_reports`, where a valid revision_id comes from, and behavior on a missing revision are all absent for a two-parameter 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 must carry parameter meaning and largely does not. `revision_id` is only conveyed through a regex pattern, with no explanation of its `rev_...` origin, and `include_unreviewed_reports` is never addressed at all — the mention of 'review state' and 'outcome reports' only obliquely hints that reports can be filtered by review status.

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?

Names a specific verb and resource ('Read one exact revision of a Noosphere record') and enumerates exactly what is returned: body, sources, conditions, content hash, review state, outcome reports. The word 'exact' plus the revision_id requirement implicitly separates it from the fuzzy `search` sibling, but no sibling is named explicitly.

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 phrase 'one exact revision' implies a by-ID lookup that follows a `search` or `propose_revision`, so the usage context is inferable. However, there is no explicit when-to-use/when-not statement, no mention of what to do if the ID is unknown, and none of the siblings (annotate, report_outcome, search) are referenced.

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