search_conversations

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

The description mentions core capabilities but lacks detail on read-only nature, pagination, or error handling. Without annotations, it partially covers behavioral aspects but misses important transparency on side effects or limitations.

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?

A single, front-loaded sentence that is concise and information-dense, with no wasted words.

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?

Despite high schema coverage, the description is too brief for a tool with 8 parameters and no output schema. It fails to explain return format, how context windows behave, or how time ranges interact, leaving gaps for the agent.

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%, so baseline is 3. The description adds minimal semantic value beyond listing features already detailed in parameter descriptions, not significantly enhancing 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 explicitly states the verb 'Search', the resource 'conversations', and highlights key features (context windows, role filtering, time ranges), clearly distinguishing from sibling tools like 'analyze_sessions' and 'summarize_daily_conversations'.

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?

No guidance on when to use this tool versus alternatives among the listed siblings. It does not specify which scenarios are appropriate for search vs. analysis or summary tools.

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