get_icon_set

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 states the tool retrieves information, implying a read-only operation, but does not disclose behavioral traits such as error handling (e.g., what happens if an invalid prefix is provided), rate limits, authentication needs, or the format of the returned data. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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 appropriately sized with two sentences: the first states the purpose and scope, and the second provides parameter guidance. Each sentence earns its place by adding value without redundancy, making it front-loaded and efficient.

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 has no annotations, no output schema, and low schema description coverage (0%), the description is incomplete. It covers the basic purpose and parameter meaning but lacks critical context such as return value format, error conditions, or behavioral details needed for effective use. This is inadequate for a tool with one parameter and no structured support.

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 input schema has 0% description coverage, with one parameter 'prefix' undocumented in the schema. The description adds meaning by explaining that 'prefix' refers to 'the icon set prefix (e.g., 'mdi', 'fa', 'bi')', providing essential semantics. However, it does not fully compensate for the coverage gap, as it lacks details on constraints (e.g., valid prefixes, case sensitivity) or examples beyond the listed ones.

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 'Retrieve' and the resource 'detailed information about a specific icon set including all available icons in that set', making the purpose specific. It distinguishes from sibling tools like 'get_all_icon_sets' (which retrieves multiple sets) and 'search_icons' (which searches across icons), establishing clear differentiation.

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 clear context by specifying 'Provide the icon set prefix (e.g., 'mdi', 'fa', 'bi')', which indicates when to use this tool (for a specific icon set). However, it does not explicitly state when not to use it or name alternatives like 'get_all_icon_sets' for broader retrieval, missing full explicit guidance.

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