vector_store_vector_search

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

With no annotations, the description discloses return format and sorting behavior but does not explicitly state whether the tool is read-only or has side effects. It adds moderate transparency beyond the name but lacks full behavioral context.

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 very concise: one sentence with metric options and return format. It is front-loaded with the core action. Could be slightly more structured but is 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?

Given the tool has 5 parameters and no schema descriptions, the description covers the main purpose and return format, but lacks details on how to use 'name', 'query' (e.g., array format), 'top_k', and 'threshold'. The output schema exists but is not shown, so completeness is moderate.

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 0%, so the description must compensate. It adds meaning for the 'metric' parameter (listing allowed values) but provides no explanation for 'name', 'query', 'top_k', or 'threshold', leaving gaps in understanding.

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's purpose: 'Find nearest neighbours' in a vector store, with supported metrics (cosine, euclidean, dot) and return format. It unambiguously distinguishes it from sibling tools like vector_store_vector_add or vector_store_vector_delete.

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?

No guidance on when to use this tool versus alternatives (e.g., other vector store operations). The description does not mention prerequisites, contraindications, or scenarios where another tool would be preferable.

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