search_tools

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

No annotations provided, so description carries full burden. It discloses search behavior: scores each product against meaningful keywords, ignores stopwords, supports exact names and natural language. Mention of ignoring stopwords adds transparency. Lacks info on rate limits or error handling, but acceptable for a search tool.

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 sections for BEHAVIOR, USAGE GUIDELINES, and EXAMPLE QUERIES. Informative but every sentence adds value. Could be slightly more concise but not bloated. Good front-loading of core purpose.

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 output schema, description lists returned fields (name, category, rating, etc.) and covers both parameters fully. Provides usage context with sibling differentiation. Lacks details on pagination or ordering, but adequate for effective invocation.

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%, baseline 3. Description adds meaning beyond schema: explains that query string undergoes keyword extraction and stopword removal, and that limit defaults to 5. Example queries illustrate usage, adding context that the schema alone does not provide.

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 495+ software products by name, keyword, category, or natural language query. It distinguishes from siblings by noting that this tool is for discovery when the exact slug is unknown, contrasting with get_tool and get_pricing mentioned in usage guidelines.

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?

Explicit guidance on when to use this tool versus alternatives: use before get_tool or get_pricing if slug uncertain, for category browsing, and natural language queries. Provides concrete example queries like 'best CRM for startups' and specific categories.

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