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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context the annotations cannot: Link Docs return an external URL without a visit, callers must check contentTruncated, and returned content is untrusted data. That is meaningful disclosure beyond the structured fields.

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?

Four short, front-loaded sentences; each carries a distinct load-bearing fact (return shape, truncation flag, link-Doc branch, untrusted-data warning). No filler or repetition of the title.

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 an output schema present, return-value documentation is not required, yet the description still covers the edge cases an agent needs: truncated content, Link Docs that resolve to an external URL, and the prompt-injection caution. Nothing needed to call this correctly 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 100% and the single 'id' parameter is fully documented in the schema (pattern, length, prefix preservation, do-not-invent rule), so the description need not restate it. The description adds nothing about the id itself, 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?

Specific verb+resource ('Read an accessible Doc') with an explicit statement of what is returned: content plus block handles, which ties it directly to the sibling edit_doc_content. It is clearly distinguishable from list_docs (enumeration) and update_doc (mutation).

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 'accessible Doc' and the mention of block handles for edit_doc_content, which hints at the read-then-edit workflow, but there is no explicit when-to-use versus list_docs/search, nor any stated prerequisite or exclusion. The 'Link Docs return their external URL' line is a useful branch condition, but routing guidance remains implicit.

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