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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that: the result set is limited to active ICPs, ordered with the built-in Primary Market ICP first, includes the current published version and a targeting summary, and explains the profile_ready flag.

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 sentences, front-loaded with what is listed and how results are ordered, followed by the calling convention and the one status flag an agent could misread. Nothing is redundant with the title or 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, the description must convey the shape of the response, and it does: identity, published version, targeting summary, and profile_ready. It could go slightly further by noting that each entry carries an id usable with getIcp or with the archive/publish siblings, but nothing critical is missing for correct invocation.

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 are zero parameters and the schema is fully specified, so the baseline is 4. The description instead spends its words on return-content semantics, which is the right use of space for a no-argument lister.

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 ('Lists') plus a precisely scoped resource ('the workspace's active ICPs') and adds ordering ('starting with its built-in Primary Market ICP'), which cleanly separates it from siblings like getIcp, listIcpVersions, and listIcpProducts.

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 gives explicit behavioral guidance for the common lookup case ('When asked what ICPs exist, name every one'), which tells the agent how to use the results. It stops short of naming alternatives such as getIcp for detail or listIcpVersions for history, so the when-not guidance is implied rather than stated.

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