Search All Sessions

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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful output characteristic — 'Returns session indicators, not full content' — which tells the agent to expect identifiers rather than payloads. However, it says nothing about read-only nature, permissions, or result ordering.

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 short sentences, zero filler, with the return-shape caveat placed immediately after the purpose statement.

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?

With no output schema, the description does address the return type ('session indicators'), which is the key missing piece otherwise. It could say more about result shape or ordering, but for a simple three-parameter search tool it is largely sufficient.

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 the baseline is 3. The description adds 'matching a keyword' while the schema states the query searches content, tags, and modes across all sessions — a slight narrowing that the schema does not confirm, and pagination parameters go unmentioned.

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?

States a specific verb (search) and resource (sessions) with a scope qualifier — thoughts matching a keyword across all sessions. The sibling search_in_session is implicitly differentiated by the 'all sessions' framing, though it is never named explicitly.

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?

Usage is implied by the 'all sessions' scope and the contrast with the per-session sibling, but there is no explicit when-to-use or when-not-to-use statement or named alternative.

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