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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the call is anonymous and read-only, and returned content is 'untrusted inert data', which is a genuine security/trust trait an agent must know. It does not cover paging behavior, but that is minor.

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?

Front-loaded with the core what/scope, then the pinning constraint, then the read-broadly guidance, then the safety note. Mostly tight, though the 'applicability, limitations, environments, negative results, outcomes and contributor feedback' list is dense and slightly padded.

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?

An output schema exists, so return values need not be explained. Combined with annotations and full param coverage, the description supplies the remaining essentials: allowed kinds, exact-id/revision pinning, and the untrusted-anonymous read posture. Complete enough for correct invocation of this moderately simple 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 100%, so the schema already documents kind, id, page, limit, and the optional revision pin. The description only echoes the id/revision pinning idea and adds no format or constraint detail beyond the schema, so the baseline 3 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 states a specific verb and resource ('Read one canonical record') and enumerates the concrete record kinds, so the agent knows exactly what is returned. It implicitly contrasts with the search sibling by emphasizing a single exact record pinned by id and revision, though it never names 'search' explicitly as the alternative.

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 hints at the workflow ('Pin the exact id and revision you rely on'; the schema notes the id comes 'from search or a link'), which implies fetch follows a search. However, it gives no explicit when-to-use vs. search/get_changes guidance and no exclusions, leaving routing to inference.

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