vector_search_hash

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

Since no annotations are provided, the description carries full burden. It states it returns 'a list of matched documents or an error message' but does not disclose side effects, performance characteristics, or confirm read-only nature. The operation is inherently a search, but transparency is adequate but not comprehensive.

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: a one-sentence summary followed by a structured Args list and Returns. It is front-loaded with the core purpose, and every sentence adds value without 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?

Given the complexity of KNN search and the presence of an output schema (as per context signals), the description provides essential details: version requirement, defaults, and parameter explanations. It could mention ordering or error specifics, but the output schema likely covers return format.

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 compensates well by explaining each parameter: query_vector as 'List of floats', defaults for index_name, vector_field, k, and return_fields. It adds domain context like 'KNN' and 'Redis 8', going beyond schema definitions.

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 'Perform a KNN vector similarity search using Redis 8 or later version on vectors stored in hash data structures.' It specifies the verb (perform), resource (vectors in hash), and distinguishes from sibling tools like create_vector_index_hash and set_vector_in_hash.

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 lacks guidance on when to use this tool versus alternatives. It mentions a version requirement but does not explain when KNN search is appropriate or how it differs from other search/retrieval tools. No exclusions or alternatives are suggested.

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