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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully discloses the result fields, style semantics, and licensing requirement (attribution). It does not mention pagination behavior or result ordering, but those are partly covered by the schema and are less critical 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?

The description is compact and front-loaded, opening with the search scope and returning immediately to what the caller gets. The remaining sentences cover styles and licensing without redundancy, so every sentence earns its place.

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?

The tool has a moderate complexity level with pagination, styles, and multiple URL outputs, and no output schema. The description covers the main return fields and style choices, and the schema covers parameter details. It is complete enough for correct invocation, though it does not describe the pagination flow or expected response shape beyond field names.

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%, so the baseline is 3. The description adds value beyond the schema by explaining what each style value visually means (e.g., outline is black line, fill is black solid), enriching the enum semantics. The query, limit, and offset parameters are already well-documented in the schema.

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 tool searches a large icon library and returns matches with IDs and URLs, making the core purpose obvious. It does not explicitly differentiate from sibling tools like related_icons or popular_icons, but the search-focused verb and resource scope are specific and unambiguous.

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 gives clear context: use this tool to find icons by keyword, optionally restricted by style, with pagination available. It does not explicitly state when not to use it or name alternatives, but the intended use case is strongly implied by the query examples and return details.

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