vector_store_list

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does disclose the conditional behavior—empty collection lists names/counts; non-empty lists documents—and the limit parameter's effect. However, it omits any mention of read-only guarantees, permissions, or return format, leaving some ambiguity about what 'list documents' returns.

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 compact and front-loaded with the main purpose. The two-sentence overview plus a short Args list contains no filler and each line contributes meaning.

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?

With an output schema present, return values need not be explained. The description covers both operational modes and the limit parameter, which is complete for a straightforward listing tool. Minor gaps exist around pagination or large result sets, but the core information is present.

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 provides only types and defaults, so the description compensates fully. The Args section explains that 'collection' switches between two listing modes and 'limit' caps rows, adding crucial semantics beyond the schema's minimal metadata.

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 lists collections or documents, using the active verb 'List' and specific resources 'collections' and 'documents'. It distinguishes itself from sibling tools like vector_store_add and vector_store_search by focusing solely on listing behavior.

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 explains the two listing modes based on the 'collection' parameter, providing clear context for when to use each mode. However, it does not explicitly compare this tool to alternatives like vector_store_search or provide exclusion criteria, so guidance is implied rather than explicit.

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