remove_members_from_segment

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

Adds behavioral details beyond annotations: 'Non-existent members silently skipped' and 'Returns 404 if invalid IDs'. Annotations only indicate not read-only, not idempotent, not destructive, but description adds error handling and side effects.

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?

Front-loaded with purpose, then structured with bullet points for args and return. Every sentence adds value; no fluff.

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?

Covers constraints (static only, silent skip), error handling, and return fields (total_added, total_removed, errors). Missing description for optional 'account' parameter, but overall complete for a mutation tool with output schema.

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 has 0% description coverage, but description explains list_id (10-char alphanumeric, from list_audiences), segment_id (numeric string, from list_segments), and emails (comma-separated). Optional 'account' parameter not described, but main parameters well documented.

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?

Description uses specific verb 'Remove' and resource 'members from a static segment or tag'. Clearly distinguishes from 'tag_member' for single-member removal and states members remain in audience, differentiating from sibling tools like 'delete_member'.

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?

Explicitly states 'Only works on static segments (tags), not dynamic segments' and provides alternative 'Use tag_member with tags_to_remove for single-member removal'.

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