memshelf_search

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the tool is safe. The description adds valuable behavioral context: it returns 'addresses and snippets' and handles 'split episodes at the section level', which goes beyond the annotations.

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?

Two sentences that are front-loaded with the core purpose. Every phrase earns its place: 'Grep the shelf' is vivid, 'every query token' clarifies behavior, and 'returns their addresses and snippets' explains output. No waste.

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 presence of an output schema (though not shown), the description covers the main return values (addresses, snippets) and a special case (split episodes). It is complete for a search tool, though it could mention snippet length limits or pagination were that relevant.

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 already provides descriptions for query ('Space-separated tokens; a hit must contain all of them') and shelf_path ('Path to an initialized memory shelf'). The description does not add further parameter details, so it meets the baseline but does not enhance understanding.

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's function: 'Grep the shelf for episodes matching every query token; returns their addresses and snippets.' It uses a specific verb ('grep') and resource ('shelf for episodes'), and distinguishes itself from siblings like memshelf_recall or memshelf_import by focusing on search.

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 for searching episodes by tokens, but does not explicitly state when to use this tool versus alternatives like memshelf_recall or memshelf_index. No exclusions or prerequisites are provided.

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