search_notes

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

No annotations, but description covers return format (snippets) and purpose. Does not disclose behavior like case sensitivity, indexing, or performance for large vaults. Adequate but not comprehensive.

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?

Three concise sentences, no fluff, well-structured. All information is relevant and 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?

Given no output schema, description adequately covers purpose, parameters, and return format (snippets). Lacks mention of pagination behavior with offset/limit, but schema covers that. Fairly complete for a search tool.

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%, so the schema already explains parameters fully. Description adds minor clarification for 'query' (can be natural language) but does not add significant value beyond schema.

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 states specific verb (search) and resource (notes) with method (full-text search) and outcome (returns matching notes with snippets). Clearly distinguishes from sibling tools like list_notes or get_note.

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 states when to use: 'Use this to find notes by content, keywords, or phrases.' However, does not provide when-not-to-use or mention alternatives like list_notes for navigation.

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