notes_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It does not cover critical aspects like whether this is a read-only operation, potential side effects, authentication needs, rate limits, or pagination behavior, which are essential for safe and effective use.

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 a single, efficient sentence with no wasted words. It is appropriately sized and front-loaded, though its brevity contributes to inadequacy in other dimensions.

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 complexity of 5 parameters with 0% schema coverage, no annotations, no output schema, and no sibling differentiation, the description is severely incomplete. It does not provide enough information for an agent to understand how to use the tool effectively or what to expect in return.

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 description mentions 'specific filters' but does not explain any of the 5 parameters (filterGroups, properties, limit, after, sorts) or their semantics. With 0% schema description coverage, the description fails to compensate, leaving parameters undocumented and unclear in purpose.

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 'Search notes with specific filters' restates the tool name 'notes_search' with minimal elaboration, making it tautological. It specifies the resource ('notes') and action ('search') but lacks detail about what kind of search or what 'specific filters' entail, failing to distinguish it from sibling tools like 'notes_list' or other search tools.

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 is provided on when to use this tool versus alternatives. It does not mention sibling tools such as 'notes_list' for unfiltered listing or 'notes_get' for retrieving a single note, leaving the agent without context for tool selection.

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