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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the underlying endpoint (GET /subscriptions), but says nothing about pagination behavior, defaults, or result ordering, which is the kind of context annotations cannot supply.

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?

Three terse sentences, front-loaded with the resource and its fields, then filters, then endpoint. No filler; the parenthetical field list is dense but each element earns its place.

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?

No output schema exists, and the description compensates by naming the returned fields (subscriptionId, contactId, listId, status) and the filterable dimensions. Pagination is left entirely to the schema, which is acceptable given its 100% coverage, so only minor gaps remain.

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 100%, so all five parameters including limit/offset are fully documented in the schema. The description only echoes the three filter dimensions (list, contact, status) and adds no syntax or semantic detail beyond that, so it sits at the baseline.

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 ('List') and resource ('list memberships / subscriptions') and enumerates the returned fields, which separates it from sibling list tools like icontact_list_lists and icontact_list_contacts. It stops short of explicitly naming the mutation counterpart icontact_set_subscription, so differentiation is implicit rather than stated.

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?

'Filter by list, contact or status' tells the agent how to narrow results but gives no guidance on when to prefer this over sibling lookups (e.g., icontact_get_list for list metadata) or when filtering is unnecessary. Usage is implied by the available filters rather than prescribed.

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