search_session

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

With no annotations, the description fully covers behavioral traits: storage location (~/.codearchitect/sessions/), search behavior (full-text, case-insensitive, relevance scoring, sorting), and response structure (relevance score, snippets). No contradictions.

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?

Well-structured with clear sections (WHEN TO USE, STORAGE BEHAVIOR, etc.), but verbose with repeated examples (e.g., user phrases). Could be more concise while retaining key information.

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?

Despite no output schema, description details return values (relevance score, snippets, match count, metadata). Covers parameters, search behavior, and storage. Contextually complete for a search tool.

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 baseline is 3. Description adds some value like default for limit (not in schema) and format hints, but mostly repeats schema info. No major additional meaning beyond 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?

The description clearly identifies the tool as searching across sessions, using specific verb 'search' and resource 'sessions'. It distinguishes from siblings like store_session and get_session by focusing on search functionality.

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 explicit user action phrases and scenarios (e.g., 'User remembers discussing something but not the exact session name'), guiding when to use. Lacks explicit when-not-to-use and direct sibling comparison, but context is clear enough.

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