vector_store_vector_add

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

No annotations provided. Description only implies mutation ('Add') but omits side effects (e.g., overwriting, dimension constraints). Does not disclose permissions or error conditions.

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?

Single sentence plus return info. Extremely concise with no redundancy.

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?

Despite having an output schema, the description lacks detail on optional parameters (metadata, doc_id), constraints (vector dimensions), and behavior for edge cases. Incomplete for a write operation with 4 parameters.

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 0%. Description only hints at 'name' and 'vector' but does not explain 'metadata' or 'doc_id' parameters. Return value is mentioned but not parameter semantics.

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 action (add a vector), the resource (named store), and the return type ({id, name, dim}). It distinguishes from sibling tools like delete, search, and list.

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., vector_store_vector_search or vector_store_vector_get). No conditions or prerequisites mentioned.

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