add_automation_queue_subscriber

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

Annotations indicate non-readonly, non-idempotent, non-destructive. The description states the subscriber will receive the email once processed and mentions the return type (JSON describing the queued subscriber). It does not disclose whether duplicates are handled, what happens if the automation is paused, or any side effects, but adds some 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 concise and well-structured: a one-line purpose statement, a brief explanatory paragraph, then labeled Args and Returns sections. Information is front-loaded and 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?

Considering the tool has 4 parameters (3 required) and an output schema (mentioned as JSON), the description covers the core function and output format. However, it omits details like handling of duplicate queue entries, email format validation, limits, and the optional 'account' parameter's purpose. This leaves some uncertainty for complete understanding.

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 description coverage is 0%, but the description provides meaningful explanations for three of the four parameters (workflow_id, workflow_email_id, email_address). It clarifies each as 'unique id' of related entities. However, the optional 'account' parameter is not documented, leaving a gap. The description adds value but does not fully compensate for the missing schema descriptions.

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 the action 'Add a subscriber to the queue of a classic automation email' and elaborates with 'Manually enrolls a subscriber into the sending queue for a specific automation email.' The verb and resource are specific, and the tool is clearly distinguished from siblings like 'add_member' 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 provides clear context for when to use the tool (manually enrolling a subscriber into an automation email queue) but does not give any guidelines on when not to use it or suggest alternatives. It lacks prerequisites or conditions (e.g., subscriber existence, automation status) that would help the agent decide.

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