delimit_vault_search

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

No annotations provided, so description bears full burden. Clearly states 'Side effects: read-only on the vault backend' and 'gated by require_premium', disclosing both safety and access control. Also explains the vault concept as 'long-lived knowledge artifacts'.

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?

Concise and well-structured: header line, then sections for When to use, When NOT to use, Sibling contrast, Side effects. Every sentence adds value with zero 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?

With a single fully-documented parameter, an output schema (assumed present), and thorough description of usage and side effects, the tool definition is fully complete for an AI agent to select and invoke correctly.

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% and the description does not add extra meaning beyond the schema's description of 'query' as 'Search query string. Required.' Baseline 3 is appropriate as description provides no additional parameter-level detail.

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 'Search vault entries by query string (Pro)', specifying verb, resource, and scope. It explicitly distinguishes from siblings delimit_memory_search and delimit_vault_snapshot, leaving no ambiguity.

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?

Provides explicit when to use ('to retrieve stored vault content matching a search string'), when not to use ('for conversation memory use delimit_memory_search'), and sibling contrast. Also notes it's read-only and gated by require_premium.

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