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

Annotations already declare destructive=true, idempotent=false, and openWorld=true, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: a hard 1000-member cap per call and the fact that campaigns which already consumed the numbers keep them, meaning historical campaign data survives the removal.

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 clauses, front-loaded with the write marker and the core action, with no filler. Every phrase — the ID source, the batch limit, the list identifier options, the campaign note — carries distinct information.

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 three-parameter destructive-removal tool with rich annotations and no output schema, the description covers purpose, batching limit, identifier options, and downstream campaign effects. It stops short of describing partial-failure behavior or what is returned, but nothing essential to invoking it correctly appears 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?

With 0% schema description coverage, the description carries the full burden and mostly does: it explains that wp_list_member_ids are member IDs sourced from list_wp_list_members with a 1000-item ceiling, and that the target list can be addressed by numeric ID or UUID. It leaves ambiguous what happens if both list identifiers are supplied or neither is, which the schema (only member_ids required) does not resolve either.

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 states a specific verb and resource: it removes member IDs from a saved list, identified by either wp_list_id or wp_list_uuid. The `[write]` prefix and the explicit reference to list_wp_list_members make it easy to separate from add_wp_list_members and from the parallel remove_*_list_members siblings.

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 implicitly tells the agent where the member IDs come from (list_wp_list_members) and caps the batch at 1000, which is useful operational guidance. However, it never states when to use this versus alternatives (for example, whether to edit the list or delete members elsewhere), nor any prerequisite such as owning the list.

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