Search Notes

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description restates read-only, which is redundant. It adds meaningful behavior beyond annotations: query filter syntax, default context length, and the session-active vault precedence rule.

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?

Front-loaded with the main purpose, then a compact set of filter semantics, a default, and a routing pointer. The repeated 'Read-only' is minor given annotations, but the definition is appropriately sized and all remaining sentences add information.

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?

With an output schema present, the description doesn't need to explain return shape. It covers the active-vault behavior, filter forms, default context length, and sibling alternatives, making the tool callable correctly in context.

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 `query` and `contextLength` but leaves `vaultPath` undocumented; the description fills that gap by explaining that it selects a vault and always wins over the active vault. It also adds concrete syntax for `tag:` and `path:` filters and the default context length, adding meaning beyond the 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?

States a specific verb and resource: 'Full-text search across every note in the vault.' It also singles out `tags.search` and `notes.list` as alternatives, so an agent can distinguish it from sibling search/list tools.

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?

Gives explicit routing guidance: for pure tag or date filtering, `tags.search` and `notes.list` are faster, implying notes.search is for full-text search. It also specifies that it operates on the session-active vault and that `vaultPath` overrides the active vault.

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