remove_members_from_segment

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

With no annotations, description bears full burden. Discloses silent skipping of non-existent members, 404 error for invalid IDs, read-only/dry-run support, and return format with total_removed and errors.

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?

Well-structured with summary, bullet constraints, then Args/Returns sections. Every sentence serves a purpose; no redundant 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?

Despite no annotations, description fully covers purpose, constraints, errors, auth, concurrency, and return format. Makes tool self-contained for correct invocation.

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?

All three parameters (list_id, segment_id, emails) have detailed descriptions including format, examples, and source (e.g., 'Obtain from list_audiences'), vastly supplementing the schema which only has titles and types.

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?

Clearly states verb (remove), resource (members from static segment/tag), and distinguishes that members remain in audience, not removed from list. Explicitly differentiates from dynamic segments.

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 when to use (static segments only), when not to use (dynamic segments), provides alternative (tag_member for single removal), and includes constraints like max 10 concurrent requests and auth method.

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