search_sessions

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

With no annotations, the description carries full burden. It discloses the scope of data ('complete raw transcripts', 'discussion, reasoning, failed approaches') and the semantic search nature. It does not mention any destructive actions or potential privacy concerns, but for a read-only search tool, the disclosure is sufficient.

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 four sentences, starting with the core purpose and then usage guidance. Every sentence contributes meaning, though it could be slightly trimmed without loss.

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?

The description adequately explains the tool's function and when to use it, but it does not describe the return value format or content. The schema hints at output via parameters like max_sessions and max_chunks, but without an output schema, the description should explicitly state what is returned (e.g., matching sessions with chunks).

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?

Schema coverage is 100% with detailed parameter descriptions. The tool description adds context about the underlying data ('complete raw transcripts') that enriches understanding of what the 'query' parameter searches over, going beyond the schema's literal 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 clearly states the tool searches 'full conversation history from past Claude Code sessions' and specifies the exact storage location. It distinguishes itself from built-in memory by claiming to be 'much more detailed', which is useful even though no siblings are listed.

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 explicitly tells when to use the tool first, listing example phrases like 'what did we discuss' and 'remember when we'. It also explains that searches are semantic, reducing the need for exact words, which is a clear usage recommendation.

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