search_conversations

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

Describes search behavior and special logic for empty term with role. However, lacks any mention of read-only nature, response structure, or performance characteristics, which is notable given no 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?

Concise description with a clear one-line summary followed by parameter details. Could streamline by merging but overall efficient.

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?

Covers all parameters with special logic, and with output schema provided, needs no return description. However, lacks hint about search matching (fuzzy/exact) or performance, which could affect agent's decision to use it in time-sensitive contexts.

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 has zero description coverage, but the tool description fully explains all three parameters including default values, special behavior, and role filtering logic. This is exceptional value beyond the schema.

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?

Clearly states it performs full-text search across conversation messages, distinguishing it from search over documents or summaries. However, it does not explicitly contrast with sibling tools like semantic_search or unified_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?

Provides usage context for empty term and role filtering but lacks explicit when-to-use and when-not-to-use guidance compared to sibling tools like semantic_search or unified_search.

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