vault_search

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

With no annotations, the description carries the full transparency burden. It explains the search modes, filter structure, default limit, and the shape of returned results, which is substantial behavioral detail. It doesn't cover edge cases like performance or error handling, but those are less critical for a search tool.

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 compact: an introductory sentence plus a structured arg list and a return summary. Every line adds value without bloating, and the key action is front-loaded.

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 tool is well-specified given its complexity. The description covers all parameters, modes, filters, and return fields, while the presence of an output schema presumably handles structural details. No significant gaps.

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?

The schema has zero descriptions, so the description's parameter explanations are essential. It defines 'query', gives a filter example, describes mode with underlying technologies (FTS5, vector, hybrid), and states default limit, fully compensating for the schema gap.

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 opens with a specific verb and resource: 'Search the vault by keyword, semantic similarity, or both.' This clearly distinguishes it from sibling tools like vault_read and vault_list by emphasizing search with multiple modes.

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?

It provides clear context for when to use the tool (searching the vault) and explains the available modes and filtering. It does not explicitly mention alternatives or exclusion cases, but the sibling list makes the tool's niche evident.

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