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

Annotations already establish readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by disclosing the return payload contains titles, tags, chunk counts, and status. It does not mention pagination, ordering, or potential absence of documents, which would be more transparent for a zero-parameter 'list all' operation.

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 sentences, no filler, and the primary action is stated first. The second sentence enumerates the return fields without unnecessary elaboration. Every sentence earns its place.

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 no-parameter read-only list tool, the description is largely complete: it states the resource scope, the action, and the returned data fields. Since no output schema exists, the return-field list is important and provided. The only gap is guidance on large result sets or ordering, which is a minor omission for this simple tool.

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 has zero parameters and the schema confirms this, so there are no parameter semantics to document. The description reasonably focuses on the output instead, which is the only meaningful facet an agent needs to understand.

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 uses a specific verb and resource, 'List all documents in the user's Dokpod vault,' making the core action unmistakable. It also names the returned fields, which separates it from media-focused siblings like list_media and search-focused tools like semantic_search. It does not explicitly contrast with siblings, so it stops short of a 5.

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 clearly implies this is the tool for retrieving an unfiltered overview of all vault documents, with no parameters to narrow scope. However, it provides no explicit guidance about when to prefer find_documents_by_name or semantic_search instead. Usage context is present but alternatives and exclusions are left to inference.

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