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

Annotations include readOnlyHint=true and openWorldHint=false, which already establish this as a safe, non-mutating operation. The description adds value beyond annotations by disclosing the return format ('full Markdown text') and clarifying that it returns complete content rather than a snippet. No contradiction exists between the description and annotations.

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?

The description is two tight sentences with zero wasted words. The first sentence front-loads the core purpose (read full Markdown page), and the second earns its place by adding usage guidance. Each sentence contributes distinct value.

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 1-parameter read tool with rich annotations, a fully descriptive schema, and an output schema present, the description covers the essential context: what it does and when to prefer it over search. The only minor gap is that it does not reference list_doc_sections, one of the sibling tools, so the full alternative landscape is not explicitly mapped.

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% — the single 'path' parameter is thoroughly documented with examples ('/quickstart', '/api/memory/add', or full URL). With such high schema coverage, the baseline is 3, and the description does not need to compensate. The description adds no additional parameter-level meaning beyond what the schema already provides.

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+resource: 'Read the full Markdown text of one documentation page.' It clearly defines the scope (full text, Markdown format) and distinguishes from the search sibling by noting it is preferred over a 'search snippet' when exact details are needed. This differentiates the tool from search_docs and makes its purpose unambiguous.

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 second sentence provides a clear context rule: 'Prefer this over a search snippet when you need exact method names, parameters, fields or limits.' This is explicit when-to-use guidance that implicitly identifies search_docs as the alternative. However, it does not explicitly name the sibling tools or state when not to use it, so it falls just short of a 5.

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