Search Notes

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

Annotations already declare read-only, idempotent, non-destructive. Description adds contextual detail: vaultPath override logic and the effect of contextLength on returned context. No contradictions.

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?

Four sentences, each serving a distinct purpose: purpose, query syntax, parameter default, vault override. No unnecessary words. Front-loaded with the primary action.

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 complexity (full-text search with filters, vault targeting) and the presence of an output schema and annotations, the description covers all critical aspects: what it searches, how to filter, default behavior, vault selection, and relationship to sibling tools.

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 covers 67% of parameters with descriptions. Description adds concrete examples for query filters (tag:, path:) and explains vaultPath's overriding behavior. The contextLength default is stated, complementing the schema's integer type specification.

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 the tool does full-text search across all notes. It distinguishes from siblings by mentioning faster alternatives for specific cases and the optional vaultPath argument. The first sentence alone conveys the core purpose.

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 provides when-not-to-use: 'For pure tag or date filtering, tags.search and notes.list are faster.' Also clarifies vault targeting behavior with vaultPath versus session-active vault.

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