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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely non-obvious behavior beyond that: a no-page call returns a TOC rather than content for long documents, and responses carry a trailing pagination hint. It does not mention error behavior for missing files.

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 core capability first and the pagination protocol second; every clause carries actionable information and nothing is repeated from the schema.

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?

An output schema exists and handles return-value explanation, and the description covers the tricky part — the TOC-then-paginate protocol. What is missing is identification of the file/project inputs and failure modes.

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 explains `page` well (default behavior = TOC, page=N = section, iterative pagination) but says nothing about `filename` or `project_id`, leaving two required parameters to inference from their names alone.

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?

Names a specific verb and resource — reading file text from the project knowledge base, delivered in pages. It implicitly separates itself from siblings like read_map_section and read_journal by scoping to files, but never names an alternative explicitly.

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?

Gives concrete operational guidance: call without `page` on a long document to get a table of contents, pick a section, then call with page=N and keep paginating per the hint at the end of the response. Clear context for the workflow, though no when-not-to-use case or named alternative tool.

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