dero_docs_list

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

Annotations already signal read-only and non-destructive behavior, and the description adds the output contract including the returned shape and the 'bundled' aspect of the docs pages. It also documents limit defaults and max, covering important behavioral details beyond 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?

The description is well organized: a one-line summary, a usage section, input requirements, and an output shape. Every sentence earns its place, and the most important guidance is front-loaded.

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 has only two optional parameters and no output schema, so the description carries the burden of explaining behavior and return values. It fully covers what the tool lists, when to call it, how to filter, and what the response looks like, and also names relevant sibling alternatives.

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%: both product and limit are already fully described in the schema. The description mostly restates the same information, though it usefully frames product as an optional scoping parameter and repeats the limit default/max. This meets the baseline but adds little new semantic value.

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 first sentence states a specific verb ('list') and resource ('indexed bundled docs pages across all four products') and names the key output fields (slugs, titles, canonical URLs). It also distinguishes itself from sibling tools by explicitly contrasting with dero_docs_search and dero_docs_get_page.

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 'When to call' guidance with concrete examples and a clear preference rule: use dero_docs_search for specific questions, use this tool for surveying or obtaining a slug catalog. This fully routes the agent to the correct sibling.

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