search_vault

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

No annotations provided, so description bears full burden. It discloses the retrieval method (hybrid) and output format (cited passages). It doesn't explicitly state it's read-only, but 'returns' implies no side effects. Could be improved by noting no modifications, but adequate.

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, 18 words, efficiently conveys purpose, method, and output. No wasted words or redundancy. Front-loaded with key information.

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's simplicity (search with two parameters, no output schema needed), the description fully covers what the agent needs: what it does, how it works, and what it returns. No gaps for effective use.

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% with descriptions for both parameters ('What to search for' and max results). The description adds context about hybrid retrieval and output but adds no new meaning to the parameters beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states verb ('Search') and resource ('personal knowledge vault'), specifies hybrid retrieval method (semantic + keyword + knowledge graph), and mentions output (cited passages). Distinguishes from siblings like read_section (reads specific section) and get_entity_neighbors (graph traversal).

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 implicitly indicates that this tool is for searching the vault, but does not explicitly state when to use it versus alternatives like read_section or get_entity_neighbors. No when-not-to-use or specific filtering guidance is provided.

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