dero_docs_get_page

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

The description adds substantial behavioral detail beyond the readOnly annotation, including pagination behavior with 60000-char chunks, the content_truncated and next_offset signals, and the meaning of content_length. This tells the agent exactly how to handle long pages and what to expect across repeated calls.

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 well-structured with a one-line summary, a 'When to call' section, critical input requirements, and an output explanation. Every section carries necessary information, and the most important decision guidance appears near the top.

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?

With no output schema present, the description compensates by specifying the exact output fields and explaining pagination-related fields. It also covers practical details like example slugs and product options, making the tool fully usable without external documentation.

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?

Although the schema covers 100% of parameters, the description adds critical semantic value: slug must be non-empty and relative to pages/, product is recommended to disambiguate duplicate slugs across docs sites, and offset has detailed chunking semantics with a clear retry instruction (pass next_offset when content_truncated is true).

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 opens with a specific verb and resource: 'Get a single bundled docs page by slug, with plain-text content and headings.' It clearly distinguishes this tool from sibling dero_docs_search and dero_docs_list by focusing on fetching one page by an exact slug rather than searching or listing.

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 provides explicit usage guidance: call it AFTER dero_docs_search returns a candidate slug, or when you already have a known slug from a prior citation. It also explicitly prefers dero_docs_search when only a topic is known, making the decision boundary unambiguous.

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