vector_search

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

No annotations are provided, so the description carries full burden. It explains the three search methods but does not disclose whether the tool modifies data, requires authentication, or has rate limits. The read-only nature of search is implicit but not stated. Behavioral transparency is adequate but could be more explicit.

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 relatively concise, with a clear bullet-like listing of actions. The first sentence 'Manage search operations.' is somewhat vague but not overly wordy. Each action is described in one sentence. Minor waste could be trimmed, but overall 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?

With 14 parameters and three distinct actions, the description fails to provide guidance on which parameters are needed for each action (e.g., 'question' likely required for all, connection parameters for external DB). No mention of default behaviors for optional parameters like weights or RRF k. The output schema is present, so return values are covered, but parameter usage across actions is underexplained.

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 100%, but parameter descriptions in the schema are minimal (e.g., 'db type', 'host'). The tool description does not add significant meaning beyond the schema—it mentions 'question' but doesn't explain how to use connection parameters or weights. It barely adds value over 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 manages search operations and enumerates three distinct search actions: semantic_search, lexical_search, and search. It differentiates from the sibling tool vector_collection_management by focusing on search rather than collection management. The verb 'manage' is a bit generic, but the actions are specific and well-defined.

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 does not explicitly state when to use this tool versus alternatives. While it lists the three search methods, it offers no guidance on choosing between them or when to avoid this tool. The sibling tool's purpose is implied but not contrasted.

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