session_search

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

There are no annotations, so the description carries the burden. It discloses that the search spans ALL sessions and implies semantic, memory-style queries. However, it does not mention result format, pagination, performance characteristics, or whether this is strictly read-only beyond the word 'Search.'

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 short, front-loaded with the core action, and every sentence earns its place. The examples are compact and materially improve understanding without adding noise.

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 gives clear purpose and realistic usage examples, making it minimally viable for an agent to invoke. However, with no output schema and no annotations, the missing details about return values, handling of empty results, and the relationship between project_root and the 'ALL sessions' scope leave notable gaps.

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%, and the description does not explain type_filter or project_root. The example questions hint at query content and possibly filters like error or dead_end, but the agent must infer how project_root relates to 'ALL sessions' and when to use type_filter. The description does not adequately compensate for the lack of schema descriptions.

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 states a specific verb and resource: 'Search across ALL sessions for a query.' It also distinguishes itself from session-management siblings by emphasizing the global, cross-session scope, and the concrete example questions clarify exactly what kind of tool this is.

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 'Useful for' examples give strong, concrete guidance on when to call this tool, such as recalling decisions, errors, file edits, and dead ends. It does not explicitly say when not to use it or name alternatives, but the context is clear enough for an agent to select it appropriately.

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