list_collections

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

No annotations are provided, but the description fully discloses the two behavioral modes (list all vs. semantic search) and implies read-only operation. It does not cover rate limits or auth, but for a simple browsing tool this is adequate.

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 two short paragraphs with no wasted words. The front-loaded summary ('Browse or search available knowledge collections') immediately conveys the overall purpose, and the mode details are efficiently presented.

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's simplicity (1 optional parameter, output schema present), the description fully covers the tool's functionality. It explains both modes clearly, and the output schema handles return value details.

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 input schema has 100% coverage and describes the 'query' parameter. The description adds value beyond the schema by explaining how the parameter's presence or absence changes the tool's behavior (list all vs. search).

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 browses or searches collections, and differentiates between listing all collections (without query) and semantic search (with query). This distinguishes it from sibling tools like 'search' which does full-text document search.

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 states when to use each mode (with or without query). While it does not mention explicit when-not-to-use scenarios, the context of sibling tools implies appropriate usage. A slight improvement would be to contrast with 'search' for document-level queries.

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