i_list_collections

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

With no annotations and no output schema, the description carries the full burden, yet it discloses nothing about return shape (collection names, IDs, counts), result limits, pagination, or whether network/login state is required. Given the presence of i_check_network, i_check_auth, and i_login siblings, the absence of any auth or connectivity precondition note is a real gap.

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?

One short, front-loaded sentence with zero filler or repetition. It is efficient, though the terseness leaves room that could have been spent on differentiation instead of nothing.

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 with a fully documented schema and no output schema, the definition is minimally sufficient to attempt a call. It falls short of complete because it never clarifies how results relate to the other collection/search tools or what a caller should expect back.

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?

There is a single required parameter whose schema description ('Search keyword for collections') fully covers it at 100% coverage, so baseline 3 applies. The description adds nothing beyond that, such as matching behavior or whether empty/partial keywords are meaningful.

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 gives a specific verb ('Search') and resource ('icon collections') plus the target site, so an agent knows it queries collections rather than individual icons. It does not distinguish itself from the many search-like siblings (i_search, i_search_all, l_search, l_list_all), leaving the boundary implicit.

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?

There is no guidance on when to choose this over i_search, i_search_all, or l_list_all, and no prerequisites or exclusions are stated. The agent must infer from the resource name alone that this is the collection-level search entry point.

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