search

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

With no annotations, the description carries the full burden but only states the basic behavior: searching and returning matching days with snippets. It omits details about case sensitivity, exact vs partial matching, snippet format, or the effect of the limit parameter. This lack of behavioral context reduces transparency.

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 concise sentence front-loaded with the core functionality. It contains no unnecessary words and delivers the essential information efficiently.

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 tool's simplicity and the absence of an output schema or annotations, the description covers the primary purpose but lacks details on output format (e.g., how snippets are presented), pagination, or the behavior of the limit parameter. It is adequate but not fully complete.

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 input schema has no property descriptions (0% coverage), so the description must compensate. It adds meaning for 'query' by mentioning 'word or phrase', but it does not explain the 'limit' parameter at all. The description partially compensates for one parameter but is insufficient for the other.

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 tool searches the whole diary for a word or phrase and returns matching days with snippets. It specifies the resource (diary) and the action (search), and the scope 'whole diary' distinguishes it from sibling tools that operate on specific days or ranges.

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?

The description implies usage when you need to find entries by keyword, but it does not provide explicit guidance on when to use this tool versus alternatives like 'get_day' or 'on_this_day'. No exclusions or alternative recommendations are given.

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