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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add genuine scope expectations beyond that: it tells the agent what will NOT be returned (names, passages, private identifiers) and that counts are 'source-reported', which sets expectations about fidelity. It stops short of saying what happens when the ID is unknown or refers to a non-public document.

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 with the resource and returned fields front-loaded, followed by the negative scope. The disclaimer clause is the least informative part but still carries behavioral meaning rather than filler.

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 description must carry return-shape information and it does list the returned categories. What remains missing is behavior for non-public or unknown IDs and whether provenance here duplicates read_snapshot_provenance, leaving an agent uncertain about results in edge cases.

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?

One required parameter with 0% schema description coverage, so the description carries some burden. It does add the important qualifier that the ID must be public, but it never mentions the 'EFTA########' format that the schema's pattern encodes, so an agent reading only the description could pass a malformed ID. Partial compensation for the coverage 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?

The description names a specific verb and resource ('Read one public source document ID') and enumerates what comes back (change counts, classifications, snapshot provenance). It implicitly separates itself from search_document_metadata via 'one ... ID', but it never names the sibling it overlaps with most, read_snapshot_provenance, which also appears in its own return list.

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 explicit statement of when to use this versus search_document_metadata (lookup by known ID vs discovery) or read_snapshot_provenance (provenance is claimed here too). The only signal is the word 'one', which an agent must infer from. No preconditions, no exclusions.

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