search_context

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

With no annotations provided, the description carries full burden. It discloses the multi-modal search behavior (semantic, keyword, graph traversal), the scope (all node types), and the return format (Markdown string). This provides adequate transparency for a search tool, though it doesn't mention rate limits or auth.

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 concise (two sentences) and front-loads the key functionality. Every part is necessary: search method, scope, usage guidance, and return type.

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 complexity (multi-modal search) and lack of output schema, the description provides sufficient context: it explains what is searched, how, and what is returned. Minor gaps exist (e.g., no detail on Markdown structure or result ordering), but not critical for use.

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 100% (all 3 parameters have descriptions). The description adds no new information about parameters beyond what is in the schema. Baseline 3 is appropriate.

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 performs semantic, keyword, and graph traversal search across all node types, distinguishing it from sibling tools that target specific contexts (e.g., get_symbol_context). It specifies the output format (Markdown string) and use case (broad discovery).

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 a clear usage context ('Use for broad discovery'), but does not explicitly state when to avoid this tool or name alternatives among the siblings. The guideline is sufficient to differentiate from more specific context tools.

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