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

With no annotations, the description carries the full burden. It discloses the return format (PNG download URLs), pixel range, and transparent background, which adds value beyond the schema. However, it does not mention whether the operation is read-only, what happens on invalid IDs, or whether the URLs are direct or API-mediated, leaving some behavioral ambiguity.

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?

A single, information-dense sentence that front-loads the action and key attributes. No filler, no redundant restatement of the tool name, and every word contributes to the meaning.

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?

For a simple two-parameter tool with no output schema, the description covers the key facts: target resource, format, size range, and background transparency. It does not explain that omitting 'size' returns all sizes, but that is already stated in the schema, so the textual description is adequate.

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 schema fully documents the id and size parameters. The description adds only the transparent background detail and the size range, which is already captured by the enum. The description does not need to compensate for undocumented parameters, so the baseline score 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?

The description uses a specific verb ('Get direct PNG download URLs') and names the resource ('Infyicon icon id'). The 'PNG' designation also clearly distinguishes it from its sibling tool get_icon_svg without requiring the agent to open either schema.

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 implies the tool is used when the agent needs PNG download URLs for an icon, but it does not explicitly state when to prefer this over sibling tools such as get_icon_svg or search_icons. There is no alternative guidance or exclusions, making usage largely implicit.

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

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

With no annotations, the description carries the full burden, and it clearly states what the tool returns: 'full SVG markup' and 'ready-to-embed SVG code.' This is appropriate transparency for a simple read-like retrieval tool, covering the output without requiring more detail.

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 two compact sentences: it leads with the action and resource, provides the id format and example, and appends the return value. Every sentence adds necessary context, and there is no irrelevant detail.

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?

For a single-parameter tool with no output schema or annotations, the description covers the essential operational aspects: what it does, how to identify the parameter, where to find valid ids, and what the response is. It omits error behavior, but that is not a significant gap for such a straightforward getter.

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?

The schema already documents the id parameter with a relevant example, and the description echoes the format and adds the useful note about obtaining ids from search_icons. That is slight reinforcement but not substantial new meaning beyond 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 verb 'Get' and the resource: full SVG markup of an Infyicon icon by id. It also provides the id format and contrasts with sibling tools by specifying SVG rather than PNG or category listing.

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 by explaining the id format and directing users to get ids from search_icons. It does not explicitly list when to prefer this tool over get_icon_png, but the guidance about id acquisition supports correct usage.

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

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

There are no annotations, so the description carries the full burden. It does disclose that the output is sorted by popularity and includes icon counts, and it provides the URL slug pattern. Yet it does not specify the exact response shape, any auth requirements, or whether the limit parameter affects pagination.

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 short sentences with no filler. The core behavior is front-loaded, and the second sentence adds a directly useful URL format for the resulting category slugs.

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?

With no output schema, the description should reveal more about the response structure, such as the fields returned in each category object. The slug pattern and icon counts are hinted at, but the return shape is not clearly stated.

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?

The only parameter, 'limit', is already fully documented in the schema with min/max and default values. The description adds no additional semantic nuance, so with 100% schema coverage the baseline score 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?

The description uses a specific verb and resource: 'List the most popular Infyicon icon categories with icon counts.' It clearly distinguishes this from the sibling icon lookup/search tools, making the tool's role immediately identifiable.

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 implies when to use the tool: when a list of popular categories is needed. However, it does not explicitly place it relative to siblings like search_icons or get_icon_svg, nor does it state when not to use it.

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

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

No annotations exist, so the description must carry behavioral context. It adds that the icons are free to use with attribution, explains the available styles, and specifies the return fields (id, style, URLs). This goes beyond a generic statement and helps the agent predict outcomes, though it does not discuss ordering, pagination, or error cases.

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 composed of concise, front-loaded sentences, and each sentence contributes functional information: action, returned properties, style definitions, and licensing. It is efficient and informative, though the style enum listing unnecessarily repeats the schema.

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?

With no output schema and no annotations, the description provides a reasonable level of completeness: you know what the tool searches, what the response shape-ish, and what options exist. It does not describe when to use this tool vs. siblings, or any rate/return-limits beyond what's in schema, but for a search tool these are minor gaps.

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 useful parameter documentation (query examples, style enums, limit defaults). The description does include style names, but these duplicates schema enum and doesn't add meaning beyond it. Since the schema already carries the semantics, a 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 identifies a specific verb and resource: 'Search 161,000+ free Infyicon vector icons.' It also enumerates what is returned (icon id, style, URLs), making the purpose unambiguous. While it does not explicitly differentiate from sibling tools like uicons_lookup, the search focus is clear enough to stand apart from get_icon_svg/get_icon_png.

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 explains what the tool does but offers no guidance on when to choose it over alternatives. It does not mention, for instance, that if an agent already knows an icon's ID it should use get_icon_svg, or that list_categories should be used for category listing. Usage context is only implied, not explicitly stated.

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

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

No annotations are provided, so the description carries the burden of disclosing the operation. It correctly implies a read-only lookup and explains the output format and associated stylesheet. However, it does not mention error behavior, multiple-match semantics, or response shape beyond the single example.

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 concise, front-loaded with the core purpose, and lamppost compares efficiently. The second half supplies a concrete usage snippet and the stylesheet URL, all in two sentences with no filler.

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?

Despite lacking an output schema, the description explains what is returned (a CSS class) and how to use it, which strongly supports correct invocation. It does not go as far as describing failure or multiple-result behavior, but for a simple one-param lookup this is largely sufficient.

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?

The schema has 100% description coverage for the only parameter, `name`, which is described as a 'Glyph name to search'. The tool description adds no extra parameter semantics, only illustrating a search result. Baseline 3 applies because the schema already provides sufficient meaning.

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 ('Look up CSS class names'), the resource ('Infyicon UI webfont'), and the scale ('61,000+ glyphs'). The example output `<i class="ii-r-home"></i>` makes the purpose concrete and helps distinguish this from sibling tools that return SVG/PNG icons or list categories.

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?

It explains how to use the returned class, but does not explicitly tell an agent when to choose this tool over `search_icons` or the icon exporters. The intended use case is implied by 'CSS class names' rather than stated as a clear rule or comparison with alternatives.

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