List all available documentation topics

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds minimal behavioral context beyond that—it mentions the tool lists topics 'and their descriptions' and references fetch_self_docs, but doesn't disclose details like response format, pagination, or rate limits. With annotations covering the safety profile, a 3 is appropriate as the description adds some value but not rich behavioral context.

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 two sentences, front-loaded with the core purpose and followed by a brief usage note. Every sentence earns its place by clarifying the tool's function and its relationship to another tool, with zero wasted words.

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?

Given the tool's low complexity (0 parameters, read-only operation), annotations covering safety, and the presence of an output schema (which handles return values), the description is reasonably complete. It explains what the tool does and hints at its usage context, though it could be more explicit about differentiation from siblings like 'search_docs'.

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?

The input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. A baseline of 4 is given for tools with no parameters, as the description correctly avoids unnecessary parameter details.

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 the tool's purpose: 'List all available documentation topics and their descriptions.' It specifies the verb ('List') and resource ('documentation topics'), though it doesn't explicitly differentiate from sibling tools like 'search_docs' or 'fetch_self_docs' beyond mentioning the latter in a second sentence.

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 implied usage guidance by stating 'This tool shows you all the documentation topics you can fetch with the fetch_self_docs tool.' This suggests a relationship between listing topics and fetching them, but it doesn't explicitly state when to use this tool versus alternatives like 'search_docs' or when not to use it.

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