list_vector_db_providers

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

Description conveys it is a read-only information retrieval tool returning provider details. While no annotations exist, the description does not mention rate limits or freshness, but for a simple listing tool it is adequately transparent.

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 concise sentences with no fluff. The first states the core functionality, the second provides usage context. Front-loaded and efficient.

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 simple tool with no parameters or output schema, the description covers what is returned (required/optional fields, setup notes) and why to use it. Minor gap: does not specify return format (e.g., array of objects) but is otherwise sufficient.

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?

No parameters exist, so schema coverage is 100%. Following the rule, baseline is 3; description adds no param meaning but none is needed.

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 explicitly states the action: returns all supported vector database providers with config fields and notes. It distinguishes from siblings like list_embedding_providers and sync_to_vectordb by specifying its role as a prerequisites tool.

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?

Directly advises 'Call this before sync_to_vectordb' and explains the purpose: to understand required vector_db_config fields. This provides clear when-to-use guidance and distinguishes it from the sibling sync tool.

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