List Sources

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

Annotations are empty, so the description carries the full burden. It states the tool lists sources with capabilities, implying a read operation, but does not disclose whether it requires permissions, has pagination, or any side effects. For a simple list, this is minimally adequate but leaves gaps.

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?

Description is a single concise sentence with no fluff. Every word serves a purpose, and it is front-loaded with the main action.

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?

The tool is simple with one optional parameter and no output schema. The description mentions 'capabilities' but does not specify the return format or any details about the list (e.g., pagination, sort order). It is adequate but could be more complete for an agent to fully understand the response.

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?

Schema description coverage is 100%, and the description only repeats the optional filter capability already captured in the schema's parameter description. It adds no new meaning beyond the schema.

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?

Description clearly states the tool lists all available knowledge sources with their capabilities, and optionally filters by namespace. The verb 'List' and the resource 'knowledge sources' are specific, and the optional filter distinguishes it from sibling tools like search-knowledge (which likely searches within sources) and get-source-schema (which retrieves schema for a specific source).

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?

No guidance on when to use this tool versus siblings. For example, it does not explain when to use list-sources instead of search-knowledge or get-source-schema. The description only mentions the optional namespace filter, but no contextual cues for selection.

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