vector_search

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

With no annotations, the description must disclose behavioral traits. It reveals internal implementation details (embedding model, two similarity methods) but does not state that the operation is read-only, discuss potential side effects, or describe authorization requirements. The technical detail adds some transparency but is incomplete.

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 concise, consisting of two short sentences that front-load the core purpose. The first sentence is direct, and the second adds technical detail. However, it could be slightly more structured with bullet points for readability.

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?

The description omits what the tool returns (output shape, response format), which is critical given no output schema. It also does not explain how 'top_n' and 'context' parameters influence results beyond default values. The complexity is moderate, but the description fails to cover essential usage context.

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 coverage is 100%, so the baseline is 3. The description adds context about the embedding model (384-dim fastembed, NS_EMBED_MODEL) which is not in the schema, providing marginal added value. However, it does not explain parameter interactions or format requirements 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?

The description clearly states the tool performs semantic vector search to find similar keywords, specifying the methods (Turso vector_distance_cos or Python cosine fallback). It provides a specific verb+resource combination, but does not explicitly differentiate from siblings like 'find_candidates', though the name itself suggests the purpose.

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 is given on when to use this tool versus alternatives like 'find_candidates' or under what conditions. There is no mention of prerequisites, context requirements, or when to avoid using the tool.

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