list_icps

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

With no annotations provided, the description should disclose behavioral traits. It mentions pagination but does not state whether the tool is read-only (implied but not explicit), ordering of results, or potential rate limits. The lack of detail leaves behavioral aspects unclear.

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 extremely concise with one sentence and 11 words, front-loaded with the core action. Every word is necessary, and there is no redundancy or unnecessary information.

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?

The description lacks completeness given the absence of an output schema. It does not explain what information the response contains (e.g., list of ICP objects with fields), or how the search query (q) parameter works. The tool has 4 parameters and no output specification, so more context is needed.

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 coverage is 100% as all parameters have descriptions. The description adds no new meaning beyond the schema; it only restates pagination support already captured by page and per_page parameters. Baseline 3 is appropriate.

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 action (list), the resource (ICPs), and the scope (for a workspace). It effectively distinguishes from siblings like create_icp, delete_icp, and update_icp, and among list_* tools, it is specific to ICPs.

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 does not provide guidance on when to use this tool versus alternatives, such as when to filter by search query (q parameter) or how pagination works in practice. No when-not-to-use or alternative tool suggestions are given.

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