kb_list

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the action ('List all documents') which implies a read-only operation, but it does not mention pagination, ordering, size limits, or any edge cases like hidden or deleted documents. For a simple list tool this is adequate, but it does not add context beyond the action itself.

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?

A single, front-loaded sentence that conveys the entire purpose with zero fluff. Every word earns its place, and the output fields are listed compactly.

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?

An output schema exists, so return values are already defined. The description covers the action and scope completely for a list-all tool. There is no missing information an agent would need to decide whether to call it or interpret its result.

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, so the schema is trivially complete (100% coverage). The description adds no parameter-specific meaning because none exist, and none is needed. This meets the baseline for a parameterless tool.

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 states a specific verb ('List') and resource ('documents in the knowledge base'), and enumerates the returned fields (source_id, name, size, dates). This clearly distinguishes it from siblings like kb_search (find) and kb_get (retrieve a single document), leaving no ambiguity about its purpose.

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 implies usage: call this when you want a complete inventory of documents. However, it does not explicitly exclude alternatives or mention when to prefer kb_search or kb_get, so it lacks explicit when-not guidance. The sibling names make the distinction fairly obvious, but the description itself does not spell it out.

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