search_notes

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

No annotations provided, so the description carries full burden. It discloses date format (YYYY-MM-DD), filter logic (AND), and pagination via limit parameter. It does not mention authentication or rate limits, but as a search tool, read-only behavior is implied.

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 three sentences, front-loaded with purpose, and each sentence adds value. There is no wasted text.

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 5 parameters, none required, and an output schema exists, the description covers filtering, date format, and pagination. It does not mention sorting or scope of notes (e.g., all notes vs. per entity), but is fairly 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?

Schema coverage is 0%, so description must add meaning. It specifies date format (YYYY-MM-DD) and that limit controls pagination, adding value over the schema. However, it does not explicitly explain each parameter's purpose (e.g., created_from is start date), though parameter names are self-explanatory.

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 tool's purpose: 'Search for notes by date range.' It uses a specific verb (search) and resource (notes), and distinguishes from sibling tools like 'get_note' (single note retrieval) and 'create_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?

The description provides clear usage guidance: 'Provide at least one filter for targeted results. Filters are combined with AND logic. With no filters, returns a paginated list of recent notes.' It explains when to use filters and what happens without, but does not explicitly mention alternatives among sibling search tools.

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