search_notes

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. 'Search notes by keyword' implies a read operation but does not state whether it is read-only, case‑sensitive, or returns partial matches. There is no information about pagination, ordering, or access restrictions, which is a significant gap for a search tool.

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, front‑loaded sentence with no fluff. It is appropriately concise for a simple search tool. If anything, it is under‑specified rather than verbose, but it earns its place by clearly identifying the tool's purpose.

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 there is no output schema and no annotations, the description should explain what the tool returns and any relevant behavior. 'Search notes by keyword' does not mention the format of results, error conditions, or any filtering capabilities. For a simple tool it is still incomplete, leaving the agent to guess at the tool's behavior.

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 schema has zero description coverage for the 'query' parameter. The description adds the word 'keyword' but that is largely synonymous with 'query'. It does not clarify whether the search is substring, full‑text, exact match, or case‑insensitive. For a single required parameter, more detail was needed to compensate for the missing schema description.

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 uses a specific verb 'Search' with a resource 'notes' and a modifier 'by keyword', clearly distinguishing it from the sibling tool 'add_note' which creates notes. However, it lacks additional context about scope or behavior, making it clear but not exceptionally rich.

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 about when to use this tool versus alternatives. The description does not mention the sibling tool 'add_note' or any exclusions. It merely states what it does, implying usage without explicit direction.

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