Search notes

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

Discloses case-insensitive matching and that any note containing the query is returned. However, lacks details on return format, empty results, pagination, or limits. With no annotations, more could be said.

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?

Extremely concise: two sentences with no wasted words. Every part adds clarity.

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 simplicity (1 parameter, no output schema), description adequately covers purpose and matching behavior. Minor gap: not specifying what fields are returned (e.g., full note or IDs).

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 100% with a basic description for 'query'. The tool description adds value by specifying case-insensitive search and the behavior of matching against text, going 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?

Clearly states the verb 'search' and resource 'notes', with specific behavior (case-insensitive text matching). Distinguishes from siblings like add_note, list_notes, complete_note, delete_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?

Implied usage for keyword-based search, but no explicit when-not-to-use or alternatives. Lacks exclusions or context on when list_notes would be more appropriate.

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