add_automation_queue_subscriber

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

Annotation declares readOnlyHint=false, which is consistent with mutation. Description adds that it respects read-only/dry-run modes and has a max 10 concurrent requests, providing useful behavioral context beyond annotations.

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 one-line summary, a concise paragraph, bullet-pointed args, and returns section. 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?

The description covers all parameters, authentication, rate limits, and return format. With an output schema present, the return description is sufficient. Missing error conditions or idempotency, but still fairly complete for a simple add operation.

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?

Given 0% schema description coverage, the description compensates by explaining each parameter (workflow_id, workflow_email_id, email_address, account) with meaningful descriptions, including account's optional nature and configuration hint.

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 the tool adds a subscriber to the queue of a classic automation email, using a specific verb and resource. It distinguishes from sibling tools like add_member or batch_subscribe by specifying 'automation email queue' and 'classic automation'.

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 implies when to use (manually enroll to automation email queue) but does not explicitly mention alternatives or when not to use. It lacks guidance distinguishing it from similar operations like add_member or batch_subscribe.

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