Session Search

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

The description adds context about using an FTS5 index for cross-session recall, but does not disclose behavioral traits beyond what annotations (readOnlyHint) already provide. No mention of pagination, sorting, or response format.

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 concise sentences front-load the purpose and method. Every word is necessary; no redundancy. Excellent structure.

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 simplicity of the tool (2 parameters, no output schema), the description is nearly complete. It covers the core functionality and context (FTS5 index, cross-session recall). Minor omission: default limit value is only in schema, not description.

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 100% coverage with descriptions for both 'query' and 'limit'. The description does not add additional meaning or clarify parameter semantics beyond what the schema offers.

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', the resource 'past session notes and conversations', and the method 'full-text search using SQLite FTS5 index'. This effectively distinguishes it from sibling tools like search_lessons, which target a different domain.

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 cross-session recall but does not explicitly specify when to use this tool versus alternatives like search_lessons. No when-not-to-use or alternative guidance is provided.

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