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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, so safety framing is covered. The description adds value beyond them by explaining that 'pending' triggers a double opt-in confirmation flow and that the operation is gated on prior consent — real behavioral context an agent needs.

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 short sentences, front-loaded with the WRITE marker and the subscribe-vs-unsubscribe split, then the precondition, then the endpoint. No filler and nothing needing reordering.

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 still covers the mutation, both directions of the operation, the consent precondition and the status semantics. It could have said what happens when a contact is already subscribed (relying on the idempotent annotation instead) or what the response returns, but nothing critical for correct invocation is missing.

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%, so all three parameters are already documented in the schema, making baseline 3 appropriate. The description adds a little ('pending to start double opt-in') over the schema's 'pending = awaiting confirmation', but says nothing about contact_id or list_id beyond what the schema states.

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 and resource — 'put a contact on a list' or 'unsubscribe it' — with the endpoint POST /subscriptions, plus a 'WRITE:' prefix that immediately signals mutation. The set-vs-list distinction is clear enough to separate it from sibling icontact_list_subscriptions without opening either schema.

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?

'Only for contacts who agreed to receive mail' gives an explicit eligibility constraint/exclusion that guides when to call it. It does not name a sibling alternative or say what to do for contacts who have not consented, so it falls short of full routing guidance.

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