list-knowledge-sources

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is established. The description adds context about the knowledge base and its role in finding filter parameters, but it does not provide additional behavioral details such as pagination, output format, or side effects. This meets the expected bar for a simple listing tool.

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 only two sentences, front-loaded with the action verb and resource. The second sentence adds practical usage guidance without any redundant fluff. Every word contributes to the tool's understanding.

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 simple read-only listing tool with no parameters and no output schema, the description is complete: it states what is listed, where (MongoDB Assistant knowledge base), and why it is useful (exploration and finding search filter parameters). It could mention the return format, but that is not critical for a list tool with such clear purpose.

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 description coverage is vacuously 100%. Per the baseline rule for 0-parameter tools, the score is 4. The description does not need to explain parameters, and it correctly mentions that filter parameters for search-knowledge can be discovered from this 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 clearly states the tool's function: listing available data sources in the MongoDB Assistant knowledge base. It is specific with a clear verb and resource, and distinguishes itself from sibling tools like list-collections and list-databases by focusing on the knowledge base and referencing search-knowledge.

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 explicitly tells users when to use this tool: to explore data sources or to find filter parameters for search-knowledge. It provides clear context for its use, though it does not explicitly mention alternatives 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.