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

With no annotations, the description carries the full behavioral burden. It clearly discloses pagination through 'next' with null termination, enforces a max window of 40 paragraphs, and explicitly states that a missing paragraph means refusal rather than fabrication.

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 three compact sentences with no wasted words. It front-loads the core window concept, then covers parameters, continuation, and refusal behavior efficiently.

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 two-parameter read tool with no output schema, the description covers windowing, bounds, continuation, and error semantics. The only notable gap is the unspecified default for 'count', and permission/read-only context is not mentioned but is less critical here.

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 compensate. It does: 'from' is defined as a 0-based paragraph index, 'count' as the number of paragraphs capped at 40, and continuation is explained via 'next'. It does not state the default behavior when 'count' is omitted.

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 title 'Read paragraphs' and the description clearly establish a verb, resource, and scope: reading paragraph text as a window. This is distinct from sibling tools like document_apply or document_comments, and the description adds concrete mechanics via 'from' and 'count'.

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 description implies when to use the tool: to read a range of paragraphs and continue via 'next'. However, it does not explicitly mention alternatives or state when not to use it versus related document tools.

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