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

Annotations already declare destructive/non-idempotent/write/openWorld, so the bar is lower. The description adds two genuinely useful behavioral facts not in the annotations: the 1,000-member cap per call and that campaigns which already ingested the members retain them (partial-irreversibility). That's meaningful beyond what structured fields provide.

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 compact sentences with the destructive write tag front-loaded and the campaign caveat trailing. It's efficiently sized, though the parenthetical nesting of id sources is slightly dense.

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 3-parameter destructive batch mutation with no output schema, the definition covers what it removes, from where, the cap, and the campaign-retention behavior. Missing return-value info is acceptable since no output schema exists, but the id-vs-uuid semantics remain slightly under-specified.

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%, so the description must carry parameter meaning. It names voip_list_member_ids, its source (list_voip_list_members) and cap (1000), and that the list can be identified by voip_list_id or voip_list_uuid. That adds real value, though it doesn't say whether the id/uuid pair is required-together, exclusive, or optional.

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: 'Removes people ... from a saved list'. It names the exact member identifiers and clarifies the members come from list_voip_list_members, so an agent can tell what resource is being mutated. It doesn't explicitly contrast with sibling remove_email_list_members / remove_sms_list_members, but the 'voip' naming makes the channel unambiguous.

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?

Usage is strongly implied ('Removes ... from a saved list') and the note about campaigns is context, but there's no explicit when-to-use vs alternative statement or prerequisite guidance (e.g., confirm the member ids come from list_voip_list_members first, which it hints at only via parenthetical). It's adequate but not a routing guide.

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