get_icon_set

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

With no annotations, the description carries the full behavioral burden. It discloses the payload content ('all available icons in that set'), which hints at a potentially very large response, but says nothing about size, pagination, permissions, caching, or behavior for an invalid prefix. That is a significant gap for a tool whose read-only nature must be inferred from 'Retrieve'.

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 tight sentences, front-loaded with the purpose and followed by the required input. The second sentence largely restates the schema's parameter description, but it is short enough that the redundancy costs little.

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 one-parameter read tool this is minimally sufficient, and it does state what is returned. With no output schema, though, the shape of the returned data (fields per icon, ordering, size limits) is unexplained, and the potential volume of 'all available icons' in a large set like 'mdi' is not flagged.

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% and the single 'prefix' parameter is already documented with examples in the schema. The description's parenthetical ('mdi', 'fa', 'bi') adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Retrieve detailed information about a specific icon set') and adds scope ('including all available icons in that set'), which implicitly distinguishes it from get_all_icon_sets. However, it never names a sibling explicitly, so differentiation is left to inference from 'specific' vs 'all'.

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?

Usage is only implied: the need to supply a known prefix signals 'use this when you already know which set you want,' contrasting with get_all_icon_sets. There is no explicit when-to-use, no guidance on choosing between this and search_icons or get_icon_data, and no error case for an unknown prefix.

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