enroll_in_automation

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

With no annotations provided, the description carries the full disclosure burden and does well: it reveals that the sequence self-stops on unsubscribe/reply/bounce and that duplicate enrollment is a no-op, meaning retries are safe. It could additionally mention return behavior or error cases, but the most important behavioral traits are covered.

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?

Three concise sentences: the first states the core action, the second explains the preferred use case and its benefit, and the third covers idempotency and retry safety. Every sentence earns its place with no filler or 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 provides essential operational context such as automatic stopping and safe retries, which is helpful for a mutating tool with no annotations. However, it does not explain what a successful response looks like, what error conditions might arise, or how the optional 'variables' parameter is used, so an agent may not fully know what to expect after calling it.

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 only 33%, with only 'variables' described in the schema. The description does not clarify the semantics of 'automation_id' or 'email' beyond indirectly referring to 'a multi-step sequence' and 'someone'. Given the low coverage threshold, the description needs to compensate and does not sufficiently do so.

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 action ('Put someone into a multi-step sequence') and the resource (an automation), which is specific enough to distinguish it from one-off sending tools. It could be stronger by naming a sibling tool or explicitly saying 'automation_id', but the purpose is unambiguous.

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 gives concrete guidance on when to prefer this tool: use it instead of manually scheduling several emails, because the sequence automatically stops on unsubscribe, reply, or hard bounce. It also notes retry safety due to idempotency. It does not explicitly list exclusions or alternative sibling tools, but the guidance is clear and actionable.

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