search

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

The description discloses side effects ('read-only, safe to retry') and details the search logic: whitespace is AND, case-insensitive substring match. Since no annotations are provided, the description fully covers behavioral traits.

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 concise with two clear paragraphs: one for purpose and usage, one for an example and side effects. Every sentence is necessary and front-loaded.

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?

Even without an output schema, the description explains the return format ('unified result list with each match tagged by its resource kind'). Combined with the search logic and side effects, the description is 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?

The description adds meaning beyond the input schema by explaining what the query matches against (title, body, description, tags) and how terms are combined (AND, case-insensitive). This is valuable for proper invocation.

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 verb 'Search' and the resources (memos, todos, calendar events). It distinguishes from sibling tools by noting that for listing every item of a specific kind, one should use list_memos/list_todos/list_events instead.

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?

Explicitly says when to use: 'when the user asks an open-ended question like "find anything about X" or doesn't specify the resource type.' It also provides alternatives for specific listings.

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