vault.search_notes

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

Annotations already indicate readOnlyHint=true and openWorldHint=false. The description adds a notable behavioral trait: 'deterministic order', which informs the agent that results are consistent across calls. This goes beyond annotations.

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 one sentence, front-loaded with the action, and adds a key qualifier. It is concise but could be slightly expanded to include parameter hints without losing brevity.

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 12 sibling tools and 3 parameters with 0% schema coverage, the description lacks enough context for an agent to decide when to use this tool. Key details like default case sensitivity, pagination behavior, and result format are missing.

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 description coverage is 0%, so the description must explain parameter semantics, but it does not mention any parameters. The words 'Search note contents' only vaguely imply the query applies to content, but no details on caseSensitive, limit, or query format are provided.

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 verb 'search' and resource 'note contents', and adds the qualifier 'deterministic order' which helps distinguish from siblings like vault.list_notes. However, it does not specify whether the search is full-text or limited to specific fields.

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 is provided on when to use this tool versus alternatives such as vault.list_notes or context.retrieve. There are no exclusions, prerequisites, or context about the best use cases.

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