List icon collections

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

The annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful context beyond that: it lists the metadata returned, states that icon images are not returned, and notes that each icon set keeps its own license.

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 short and front-loaded, with the core purpose in the first sentence and exclusions immediately after. There is minor redundancy around licensing because license is both listed as returned metadata and restated at the end.

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 list operation with no output schema, the description does enough: it explains the returned metadata, states what is not returned, and points to alternatives for icons. The only minor gap is that pagination and limit behavior are left entirely to the schema.

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 all four parameters are already well documented in the schema. The description reinforces the query, prefix, and category filters but adds little beyond those schema descriptions and does not mention the limit parameter.

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 states a specific verb and resource: list Iconify collections available on Icônes. It also clarifies the returned fields and explicitly distinguishes itself from get_collection and preview_icons by saying it does not return icon images.

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 filtering guidance via query, prefix, or category, and routes image-viewing use cases to get_collection or preview_icons. It does not explicitly compare itself with search_icons, so the alternative guidance is useful but not fully exhaustive.

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