dero_docs_get_page

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

Annotations declare readOnlyHint=true, destructiveHint=false. The description adds that pages are returned in 60000-char chunks with pagination via offset, and explains content_truncated and next_offset signals. This goes beyond annotations to fully describe behavior.

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?

Well-structured with clear sections: purpose, when to call, input requirements (with CRITICAL label), and output. Every sentence adds value without redundancy. Efficiently conveys all necessary information.

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?

No output schema, but description fully explains all output fields. Covers pagination, product disambiguation, prerequisites, and edge cases. Complete for the tool's complexity and context.

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%, baseline 3. Description adds value by specifying slug must be non-empty with examples, product is recommended for disambiguation with enum values, and offset is for pagination with usage instructions. Richer than schema 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?

The description clearly states it gets a single bundled docs page by slug, with plain-text content and headings. It distinguishes from siblings like dero_docs_search and dero_docs_list by specifying that it fetches a specific page by slug, not 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?

Explicitly guides when to call: after dero_docs_search returns a candidate slug or when a known slug exists. Prefers dero_docs_search first for topic-based queries. Provides input requirements and pagination instructions for long pages.

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