search_sessions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about search behavior ('each word is matched independently and ranked by relevance'), but doesn't cover aspects like permissions, rate limits, or response format. This is adequate but has clear gaps for a search tool.

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 highly concise and front-loaded: it starts with the core purpose, followed by specific usage advice. Every sentence adds value without redundancy, making it efficient and well-structured.

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 tool's moderate complexity (search with pagination), no annotations, and an output schema (which handles return values), the description is partially complete. It covers search behavior but misses key details like pagination semantics and lacks sibling differentiation, leaving room for improvement.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It only mentions the 'query' parameter implicitly ('Use short keywords'), but doesn't explain 'limit' or 'offset' (pagination), nor does it clarify the query syntax or ranking details. This leaves significant gaps in parameter 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 purpose: 'Search across all session messages.' It specifies the resource (session messages) and verb (search), but doesn't explicitly differentiate from sibling tools like 'search_memory' or 'list_sessions,' which would require a 5.

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 provides some guidance on how to use the tool effectively ('Use short keywords, not natural language phrases'), but doesn't specify when to choose this tool over alternatives like 'search_memory' or 'list_sessions.' It implies usage context without explicit exclusions or comparisons.

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