list_automation_removed_subscribers

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

The description claims 'safe to retry', implying idempotency, but the annotation sets idempotentHint to false, creating a contradiction. This violates the transparency rule.

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 brief, well-structured with a clear first sentence, followed by details on behavior, authentication, and parameters. Every sentence adds value without redundancy.

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 is a read-only list operation with an output schema, the description covers authentication, rate limits, parameters, and return type. It lacks discussion of pagination or error handling, but is largely complete.

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 compensates by explaining both parameters: workflow_id as the unique id, and account as optional with a reference to list_accounts. This adds meaningful context beyond the schema.

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 clearly states it lists subscribers removed from a classic automation workflow, with a specific verb 'list' and resource. It distinguishes from sibling tools like 'get_automation_removed_subscriber' (single) and 'remove_automation_subscriber'.

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 explains what the tool retrieves and mentions authentication and concurrency limits. It does not explicitly state when not to use it versus alternatives, but the context is clear and it points to 'list_accounts' for account parameter guidance.

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