kb_list_sources

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

With no annotations, the description must carry the behavioral disclosure burden. 'List' implies a read-only operation and 'state of their Qdrant collections' indicates the kind of information returned. However, it does not explicitly state that it is non-mutating, requires no setup, or has no side effects. It is minimally adequate but not rich.

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 a single, direct sentence that efficiently communicates the tool's purpose. Every word earns its place, and the core action is front-loaded with 'List configured sources.' No filler or redundant phrasing is present.

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 has zero parameters and an output schema is present, the description does not need to explain return values. It captures the essential scope ('configured sources' and collection state). It could be more complete by noting how this relates to sibling tools, such as using it before reindexing, but overall it is sufficient for a simple list operation.

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 schema coverage is trivially 100%. The baseline for 0-parameter tools is 4. The description does not add parameter-specific meaning, but none is needed because there are no parameters.

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 a specific verb ('List'), a specific resource ('configured sources'), and the additional detail of 'the state of their Qdrant collections.' This distinguishes it from the sibling tools (kb_search, kb_get, kb_reindex), which imply searching, retrieving, and reindexing rather than listing sources.

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 no explicit guidance on when to use this tool versus the siblings. It does not mention scenarios like checking configured sources, verifying collection state before reindexing, or troubleshooting. Usage must be inferred from the word 'List,' so this is a clear gap.

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