remove_automation_subscriber

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

The description adds critical behavioral details beyond annotations: it states the action is permanent and irreversible ('cannot be undone'), and specifies authentication method, max concurrent requests, and compatibility with read-only/dry-run modes.

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?

The description is well-structured with a clear purpose statement, behavioral notes, and a bulleted arg list, all in a concise format without unnecessary verbosity.

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?

Given the tool's complexity (3 parameters, output schema present), the description covers purpose, parameters, behavior, authentication, and return format, making it fully complete for an agent to select and invoke correctly.

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 fully explains each parameter: workflow_id as the automation workflow ID, email_address as the subscriber email, and account as an optional multi-account selector with reference to list_accounts, providing essential context.

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 explicitly states 'Remove a subscriber from a classic automation workflow' and explains the permanent removal from the workflow, clearly distinguishing it from general list removal or other subscription modifications.

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?

The description notes the action cannot be undone and mentions authentication and concurrency limits, but does not provide explicit guidance on when to use this tool versus alternatives like 'unsubscribe_member' or 'delete_member'.

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