fuzzy_search_icons

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

No annotations are provided, so the description carries the full burden. It mentions 'fuzzy search' but doesn't explain what that entails (e.g., tolerance for typos, ranking of results). It also omits key behavioral details like whether results are paginated, the default sorting, or any rate limits. For a search tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly. Every part of the sentence earns its place by specifying the action, resource, and source.

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 moderate complexity (search with two parameters) and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior (e.g., result format, error handling) and usage context. With no annotations and incomplete behavioral transparency, it falls short of being fully complete for effective agent 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%, with clear descriptions for both parameters ('query' and 'limit') in the input schema. The description adds no additional parameter semantics beyond implying the query is for icon names. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 action ('Fuzzy Search') and resource ('icons from lucide by icon name'), making the purpose immediately understandable. It distinguishes from siblings like 'search_categories' or 'list_all_icons_by_category' by specifying it searches icons by name. However, it doesn't explicitly contrast with 'search_icons' (a sibling tool), leaving some ambiguity about the difference between 'fuzzy_search_icons' and 'search_icons'.

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 no guidance on when to use this tool versus alternatives like 'search_icons' or 'list_all_icons_by_category'. It doesn't mention prerequisites, such as needing a query term, or clarify the 'fuzzy' aspect (e.g., approximate matching vs. exact). Without this context, an agent might struggle to choose between similar tools.

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