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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only adds the scoping fact that results come from existing campaigns. It says nothing about ordering, pagination behavior, or how many records come back by default, which matters for a paged list endpoint.

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?

A single front-loaded sentence with no filler; the verb and scope lead and the rationale trails. It is efficient, though the space saved could have been spent on pagination or return-shape detail.

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 a nested parameter object, the description should explain at least what a result looks like and how paging works; it does neither. It is adequate to identify the tool's purpose but thin 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?

Schema description coverage is 0% and the single parameter is a nested query object containing limit and cursor, neither of which the description mentions. The description provides no meaning for the pagination controls or their defaults/bounds, so it fails to compensate for the coverage gap.

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?

States a specific verb (Lists) and a specific resource (product or service descriptions saved on existing campaigns), which separates it from getCampaignDescription (single campaign) and listIcpProducts (ICP product data). The intent is unambiguous, though it never names the sibling it should be preferred over.

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 clause 'so one can be reused when creating a new campaign' implies the use case and hints at a workflow with createCampaign, but it gives no explicit when-to-use/when-not-to-use rule or named alternative. An agent must infer that this is a pre-creation lookup rather than a general campaign listing.

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