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

The description thoroughly discloses the internal fallback chain (Accept negotiation, alternate markdown mirror, file conventions, final HTML-to-markdown conversion) and the bounded pagination behavior. This goes well beyond the readOnly and idempotent annotations, giving the agent a realistic expectation of how the tool behaves and what it may return.

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 a single, information-dense sentence that front-loads the core purpose and pagination behavior before the usage note. Every clause adds value, and there is 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?

The tool is moderately complex, but the description covers its purpose, input source, fallback behaviors, pagination, and the role of task_context. No output schema exists, yet the mention of 'truncated result' in the offset parameter plus the markdown return behavior is sufficient for correct invocation.

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 100%, so the parameters are already fully documented in the input schema. The description adds helpful context about pagination and the source of URLs, but it does not add substantial new 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 action ('Return one docs page as markdown') and a clear resource ('docs page'), with pagination behavior explicitly mentioned. It also distinguishes itself from siblings by referencing llms_index as the source of URLs, making its role in the tool family clear.

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 gives explicit guidance: 'Use on the URLs llms_index returns, or on any docs URL you already hold.' This clearly states when to use the tool. It does not explicitly mention llms_search as an alternative or state when not to use it, but the context is still clear enough for an agent.

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