search_notes

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

No annotations provided and the description gives zero behavioral information. It does not state whether the operation is read-only, destructive, or has side effects, nor does it mention pagination, rate limits, or return format.

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 extremely short but sacrifices clarity and usefulness. While concise in word count, it fails to front-load essential information and is underspecified.

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?

The tool has one parameter and no output schema or annotations. The description does not address return values, result format, or error handling. It is inadequate for an agent to invoke correctly.

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 description coverage is 0%. The description does not clarify what constitutes a valid query (e.g., exact match, full-text search, syntax for operators). The parameter name 'query' is somewhat self-explanatory but the description adds no value beyond the schema itself.

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 'Search notes' states verb and resource but lacks specificity about what is searched (title, content, metadata?) and how results are returned. Siblings like get_notes_by_title and list_notes suggest overlapping functionality without differentiation.

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?

No guidance on when to use this tool versus siblings like list_notes or get_notes_by_title. No context about prerequisites, input formats, or expected behavior.

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