search_notes

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

The description only states 'read-only' but does not disclose behavioral traits like required authentication, rate limits, or consequences of the search. With no annotations, the description carries full burden, yet it is minimal.

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?

The description is very concise with two sentences, no redundancy, and front-loaded key information. Every word earns its place.

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 complexity (7 parameters, hybrid search, no output schema), the description is too brief. It lacks details on result format, pagination, mode semantics, and relationship to indexing status.

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 only 14% (one parameter documented). The description does not add meaning to the 7 parameters, such as explaining folder_exclude, folder_include, or the effect of include_archived. The mode enum is not elaborated.

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 it is a read-only hybrid semantic/keyword search over the Obsidian vault, returning file-level results with matched sections. This distinguishes it from siblings like read_note (reading a specific note) and index_vault (indexing).

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?

No guidance on when to use this tool versus alternatives, when not to use it, or how to choose between modes (hybrid, semantic, keyword). The agent must infer usage from context.

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