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

Annotations already declare read-only, closed-world, idempotent, non-destructive behavior. The description adds useful context beyond annotations: documents are public only, the response includes an official source URL and deployed content checksum, and arbitrary URLs/private files are not supported.

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 tightly written sentences with the main action and scope front-loaded, followed by exclusions. Every sentence adds relevant information without repetition.

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?

For a simple one-parameter read tool with an output schema and rich annotations, the description is complete: it covers purpose, valid input source, return provenance, and unsupported inputs. Nothing essential for correct invocation is missing.

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. It does meaningfully explain that the single 'id' parameter is an ID returned by search rather than a URL, though it does not explain the individual enum document IDs beyond the enum values themselves.

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 the full public document for an ID returned by search. It adds scope and provenance details (official source URL, deployed content checksum) and explicitly excludes arbitrary URLs and private files, which distinguishes it from search and from a generic URL fetcher.

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 clearly indicates when to use the tool: for an ID returned by search, and explicitly says it does not fetch arbitrary URLs or private files. It does not compare against the sibling tools get_integration_example or get_partner_access_requirements, so alternatives are not fully addressed.

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