search_notes

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

With no annotations, description carries full burden. It reports return format, fields, and sort order, and mentions the 'omit query' behavior. However, it omits details about include_trashed parameter and pagination (limit affects results). No contradiction with 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?

Two sentences, front-loaded with purpose, then return details and usage nuance. No unnecessary words.

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?

Description covers core functionality and sort order. Output schema exists for return fields. However, it lacks details on pagination, include_trashed, and limit behavior. Given 5 parameters and complex scoping, it is somewhat incomplete compared to sibling tools.

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 0%, so description must compensate. It explains query (text search), notebook_id, tag_id (scoping), but does not describe limit or include_trashed. Only 3 of 5 parameters are partially explained.

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?

Description clearly states it searches notes by text in title/body, with optional scoping by notebook or tag. It lists the return fields and sort order, distinguishing it from siblings like list_notes (which likely lists all notes) and get_note (single note).

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?

Provides guidance on optional scoping and notes that omitting 'query' lists recent notes. Implies when to use (search) and when to use as a listing tool. However, does not explicitly compare to list_notes or mention when not to use.

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