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

Annotations already flag this as a non-idempotent, destructive write, so the description adds real value beyond them: a hard cap of 10000 per call, and the non-obvious behavior that duplicates and invalid addresses are counted rather than rejected. It doesn't describe what the response contains or whether existing subscribers are modified.

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?

One compact passage, front-loaded with the write marker and the core action, then the input modes. The nested parentheses and embedded JSON example make it denser than ideal, but no sentence is wasted.

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?

For a destructive write with no output schema and no parameter descriptions in the schema, the definition covers what an agent needs: target list, input shapes, batch limit, and duplicate/invalid handling. Missing only edge cases such as unsubscribe status and required permissions.

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?

With 0% schema description coverage, the description carries the burden well: it documents the `items` element shape (bare address or `{"email","vars"}`), explains `source="customers"`, and notes that the two list identifiers are alternatives. It leaves open whether the id/uuid are mutually exclusive and whether both can be omitted.

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 ('[write] Adds addresses to a saved list') and identifies the target by `email_list_id` or `email_list_uuid`. This clearly separates it from sibling tools like `remove_email_list_members` and `list_email_list_members`.

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 explains the two input modes (explicit `items` vs `source="customers"`), which is useful usage context, but never states when to prefer this tool over siblings such as `import_email_campaign_recipients` or when not to call it. Usage is implied rather than explicitly guided.

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