simple_search

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

Adds case-insensitivity behavior beyond schema. No annotations provided, so description carries burden. Lacks disclosure of read-only nature or potential limits (e.g., max results behavior). Adequate but not thorough.

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?

Two concise sentences, front-loaded with purpose, immediate usage guidance. No redundancy or 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?

No output schema, and description doesn't specify return format (e.g., file paths, snippets). Adequate for simplicity but leaves uncertainty about result structure.

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 baseline 3. Description adds value by noting case-insensitivity for query and context around matches for context_length, but mostly reiterates schema defaults.

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?

Clearly states 'Text/keyword search across vault files' and distinguishes from sibling tool 'search_vault' by specifying exact text matching vs semantic search.

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 contrasts with search_vault (semantic vs exact), giving clear when-to-use guidance. No explicit when-not-to-use, but sufficient for context.

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