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

The description discloses a useful fallback chain: Accept negotiation, markdown mirror, .md conventions, then bounded HTML-to-markdown conversion. This is meaningful behavioral context beyond the annotations, and it aligns with the read-only, idempotent, and non-destructive hints. It does not contradict the 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?

Two tightly packed sentences: the first front-loads the primary function and conversion strategy, the second gives usage guidance. Every clause contributes, with no filler or repetition of schema details.

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 paginated markdown fetcher, the description adequately conveys the return type, pagination behavior, and conversion pipeline. It does not describe failure modes or exact response envelope (e.g., next_offset), but the schema and annotations cover parameter and safety aspects, making the definition reasonably complete.

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%, so the schema already documents url, offset, max_chars, and task_context. The description adds only indirect context about pagination and bounded conversion, which slightly enriches offset/max_chars semantics but does not substantially go beyond what the schema 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 clearly states a specific operation: 'Return one docs page as markdown, paginated' with a precise verb and resource. It also distinguishes itself from siblings by referencing URLs from llms_index and focusing on individual page retrieval rather than index discovery or search.

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?

It explicitly instructs when to use the tool: 'Use on the URLs llms_index returns, or on any docs URL you already hold.' This gives a clear invocation context, though it does not explicitly name alternative tools or state when not to use it, so it stops short of a full exclusionary guide.

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