Retrieve every indexed document as path plus title to map the knowledge base when you need an overview, not an answer.
List every indexed document as path plus title. Use when you need a map of the knowledge base rather than an answer.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It does disclose scope ('every indexed document'), which tells the agent this is a complete, unfiltered enumeration, but it says nothing about result volume, pagination, or what happens on a very large knowledge base.
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?
Two short sentences, purpose first then usage, with no filler. Each sentence carries distinct information: what it returns and when to pick it.
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?
For a zero-parameter listing tool with no output schema, the description supplies the essential facts (full enumeration, path+title format, use case). Only the lack of any volume/pagination note keeps it from being fully complete.
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 tool takes no parameters, so there is nothing for the description to clarify beyond the schema; baseline 4 applies. The description correctly implies no filtering input is accepted.
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?
States a specific verb (List) and resource (every indexed document) and even names the return shape (path plus title). The contrast with a retrieval tool ('a map of the knowledge base rather than an answer') implicitly separates it from sibling search_docs.
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?
Gives an explicit when: use it when you need an overview/map rather than an answer. The alternative (search_docs) is implied by 'rather than an answer' but is not named explicitly, so it falls just short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.