search_notes

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

The description reveals that only non-trashed notes are searched, and empty queries return most recent results. It lists return fields. Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context beyond that.

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 two sentences with no superfluous information. Key details (scope, tag behavior, empty query, return fields) are front-loaded and concise.

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 presence of an output schema and read-only annotations, the description covers the search functionality well. Missing explanation of the 'limit' parameter is a minor gap, but overall it's sufficiently 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?

The schema has 0% parameter description coverage, so the description must compensate. It explains the 'tag' parameter (matches nested subtags) and 'query' behavior (empty = most recent), but does not mention the 'limit' parameter, leaving a gap.

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 searches non-trashed notes by title/body, with optional tag filtering and nested subtag support. It specifies behavior for empty queries and lists return fields, distinguishing it from sibling tools like read_note and list_tags.

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?

The description provides clear context for when to use the tool (searching notes with optional tag filter). It implies usage by describing tag nesting and empty query behavior, but does not explicitly compare to alternatives or state when not to use it.

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