Search Tabler Icons

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

No annotations provided; description states search returns icon metadata (names, categories, tags, styles) and implies read-only behavior. Does not disclose potential side effects or limitations beyond the search scope.

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 efficient sentences. First conveys purpose and output; second directs to next tool. No redundant information.

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?

Covers purpose, search methods, return values, and next steps. Lacks details on pagination or error handling, but sufficient for a search tool with good schema coverage.

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%. Description adds no new parameter meaning beyond schema examples; baseline rating of 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?

Clearly states verb 'Search', resource '5,000+ free Tabler icons', and methods 'by keyword, tag or category'. Differentiates from sibling get_icon by directing users to use that for actual SVG/framework code.

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?

Specifies when to use the tool (search by keyword, tag, category) and directs to get_icon for retrieval, but lacks explicit 'when not to use' guidance.

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