search_my_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 and does an excellent job. It discloses key behaviors: semantic matching (with example), relevance ranking, a 'why' explanation per hit, result contents (what was asked and a summary), and the privacy boundary ('only the user's own sessions'). This is substantial and goes beyond a minimal tool description.

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 three concise sentences: core purpose and semantics, result format, and privacy. Each sentence adds distinct information with no filler. It is front-loaded with the main action and immediately conveys what the tool does.

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 there is no output schema and no annotations, the description adequately covers what the tool does, what results look like (why line, asked query, summary), and the access scope. This is complete enough for an agent to understand when and how to invoke it without missing critical context.

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?

The schema already documents the 'query' parameter with a helpful description. The tool description adds value by explaining how the query is interpreted semantically (e.g., 'retries' finds 'exponential backoff'), enriching the meaning beyond the schema's literal field description.

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 a specific action (semantic search) over a specific resource (the user's own agent sessions) and differentiates from siblings like list_recent_sessions by emphasizing meaning-based retrieval rather than listing. The phrase 'matches by MEANING, not just keywords' adds a distinctive feature that sets it apart.

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 clear context that this tool is for finding sessions by meaning or topic, with a note about privacy. It does not explicitly list alternatives or exclusions, but the context distinguishes it from the sibling tools (list, share, unshare, pull), and the description implies it is the go-to for semantic discovery of past sessions.

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