List Collections

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that—it does not say what a collection listing contains, whether it is scoped or paginated, or why a read-only listing accepts overwrite/confirm/document_paths parameters; the "Manage collection management operations" phrasing even suggests mutation, which sits awkwardly with readOnlyHint=true.

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?

Only two sentences, but the second ("Manage collection management operations") is pure filler that restates the title and adds ambiguity rather than information. Brevity here comes from under-specification, not efficiency.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. However, the description is inadequate for a 7-parameter tool with confusing ingest-shaped parameters on a read-only listing operation—an agent has no way to know which parameters are meaningful or how the results are scoped.

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?

Nominal schema coverage is 100%, but the schema descriptions are vacuous restatements of the field names ("confirm", "db type", "overwrite"), so the coverage metric overstates real semantics. The description contributes zero parameter guidance and does not explain why a list operation exposes ingest-oriented fields like document_paths, document_contents, overwrite and include_configured_directory.

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 first clause names a specific verb and resource ("List collections"), which is enough to identify the operation. But the parenthetical "(vector_collection_management)" and the follow-up "Manage collection management operations" blur the purpose into a generic capability-group label, and nothing distinguishes this from sibling tools like vector_semantic_search or vector_lexical_search that also touch collections.

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?

There is no statement of when to call this tool, no preconditions, and no mention of alternatives among the six siblings listed. An agent must infer from the name alone that this is the discovery/introspection call before searching.

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