read_doc

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds behavior: large pages return outline, tables come in parts with header row, part parameter for pagination, and Related pages footer. No contradiction.

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?

Well-structured into paragraphs, front-loaded with core action. Each sentence adds value: section, part, table handling, cross-references. No waste.

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?

Has output schema (not shown) so return format likely covered. Description addresses purpose, param usage, edge cases (large pages, tables), cross-references, and sources. Complete given complexity and annotations.

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 coverage is low (25%). Description explains path (from search_docs), section (heading or anchor), part (for large tables), source (listed). Also explains default behavior (outline if no section). Adds essential meaning beyond schema.

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?

Clear verb 'Read' and resource 'documentation page or one section of it'. Distinguishes from siblings like search_docs (returns paths) and grep_docs. Explains optional section and part for large pages.

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?

Provides usage context: when to use section (large pages), how to handle huge tables (part), and following cross-references. Lists indexed sources. Could explicitly say when not to use, but implies alternatives.

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