search_tools

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

Discloses the hybrid retrieval method (BM25 + graph traversal + embedding) and deprioritization of previously called tools. No annotations are present, so the description carries the full burden and does so adequately, though it could mention edge cases like empty results.

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?

Description is concise (3 sentences plus Args list), front-loaded with the core purpose, and uses clear structure. No wasted words.

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 an output schema present, description does not need to explain return values. Input parameters are well-covered. The algorithm description adds depth, but could mention output format details (though schema handles that).

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 0%, so description must compensate. It does so by providing examples for 'query' and explaining 'top_k' as maximum number of tools with a default. This adds meaningful context beyond the schema titles.

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?

Description clearly states 'Search for relevant tools by natural language query', with specific verb (search) and resource (tools). It distinguishes from sibling tools like execute_tool and get_tool_schema by focusing on discovery rather than execution or introspection.

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?

Implies usage when you need to find tools via natural language, but does not explicitly state when not to use it or provide alternatives. Sibling tools cover different purposes, making context clear enough.

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