search_tools

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

With no annotations, the description adds context about hybrid semantic search and return fields (slug, description, pricing, rating). It does not disclose potential side effects (none expected), rate limits, or authentication needs. Adequate but not thorough.

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 sentences, front-loaded with the verb and resource, no unnecessary words. Every sentence adds value.

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 no annotations or output schema, the description covers the essential purpose, return values, and usage flow. It could mention that it's read-only or clarify ranking, but overall it is sufficiently 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 the schema already describes both parameters. The description adds that it uses hybrid semantic search and returns ranked tools, which provides minor additional context. 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 it searches the AI Tool Directory catalog by keyword, use case, or category, using hybrid semantic search. It distinguishes from sibling tools by positioning itself as the discovery tool, with 'then get_tool for full detail' indicating a workflow.

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 explicitly says 'Use this to discover tools, then get_tool for full detail,' which provides clear guidance on when to use this tool vs. get_tool. However, it does not mention other siblings like list_tools or find_alternatives, leaving some ambiguity.

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