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

Annotations already carry readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond that: auto-created per-agent/per-prompt collections are hidden by default, which is not stated anywhere in the schema. It omits pagination/ordering, so not a 5.

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?

Two sentences, front-loaded with the action and scope, followed by the one piece of context an agent needs to interpret the result. No filler.

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 read-only, no-required-parameter listing tool with full schema coverage and no output schema, this is nearly complete: it explains what is listed and what is filtered out. Only the return shape (fields per collection) is left unstated.

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%, so both parameters are already documented inline, making 3 the baseline. The description's 'hidden by default' note touches the include_inactive behavior but does not clarify the distinction between inactive and auto-created-hidden collections, so it adds little 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?

States a specific verb ('List') and resource ('knowledge collections in the workspace') and then defines what a collection actually is ('named groups of files used for RAG search'). This makes it unambiguous versus mutation siblings like collections_create, collections_delete, and collections_add_file.

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?

Usage is only implied: it conveys the default scope (auto-created collections hidden) but never states when to reach for this tool versus collections_list_files or collections_list_websites, nor any prerequisite. Adequate but leaves selection to inference.

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