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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds genuine behavioral context beyond them: only *published* products are returned, and each entry carries connection-specific guidance. It says nothing about ordering, result limits, or what an empty ICP returns, which matters since there is no output schema.

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, verb-first, with the exclusion in the trailing clause where it belongs. The enumerated field list ('problems, objections, signals and angles and phrases never to use') is slightly run-on in phrasing but each item earns its place by telling the agent what the payload contains.

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 and only one nested parameter, the description carries the return-shape burden and does so reasonably by naming the per-product fields. Missing are pagination/result-size behavior and confirmation of what 'context' means, which keeps it short of complete for a list endpoint.

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 0% for the single nested icpId parameter (uuid), so the schema contributes nothing beyond type and format. The description implies the identifier selects the ICP but adds no format, sourcing, or behavior detail for that parameter. Baseline 3 is the ceiling given the schema's silence and the description's only marginal compensation.

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 opens with a specific verb and resource ('Lists the published Products connected to an ICP') and enumerates the payload fields (problems, objections, signals, angles, phrases to avoid), so an agent knows exactly what comes back. It does not name sibling tools such as listIcps, listIcpVersions, or listCampaignProductDescriptions, so differentiation is only partial (via the storage_schema_version branch).

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 an explicit exclusion: for an ICP whose version has storage_schema_version 1, the ICP holds its own product details, 'so use those instead.' That is a real when-not-to-use rule. The gap is that it never names the sibling tool or field an agent should go to, leaving the redirect implicit.

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