Vault Search

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds important behavioral context: the tool is app-only, invoked through a specific server call path, and hidden from the LLM. No annotation contradiction.

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?

Extremely concise: three short lines front-load the core purpose, then add only the necessary caller and visibility context. Every sentence earns its place with no redundant filler.

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 low complexity, complete input schema, and presence of an output schema, the description covers everything needed: what it does, who calls it, and why it should not be used by the LLM. Nothing essential is missing.

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%, so the schema fully documents query, mode, and limit. The description adds no parameter-level meaning beyond what the input schema already provides, matching the baseline for high coverage.

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?

States a specific verb and resource: 'Search the vault'. The qualifier '(app-only)' and the caller context distinguish it from sibling search-like tools such as 'search', 'vault_read', and 'browse_vault', making selection unambiguous.

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?

Explicitly names the sole caller: 'Called by the SPA browser search bar via app.callServerTool()'. It also gives a clear when-not condition with 'Not visible to the LLM', so an agent knows this tool is not intended for LLM selection.

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