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

Beyond the annotations, the description discloses meaningful behavior: enrolling triggers automation steps that text/email/mail the seller (external side effects for an openWorldHint tool), it returns the enrollment state, and it requires the user's Cotlet API key with app access. These are useful additions over the readOnly/destructive hints, though the exact confirmation mechanics remain slightly vague.

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?

Content is partly duplicated: 'Add a lead to an automation' is restated as 'Adds one lead to an automation', and the 'its steps can text, email or mail the seller' clause appears twice. Roughly half the text repeats earlier sentences rather than adding new information.

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?

For a two-parameter, both-required tool with full schema coverage, the description covers purpose, side effects, the returned state, confirmation behavior and auth needs. With no output schema, it only briefly notes 'returns its state', but that is acceptable given the tool's simplicity.

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 100%, and the schema already documents lead_id (from list_leads) and automation_id (from list_automations). The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Add a lead to an automation') and further clarifies it enrolls a single lead and returns its state. This clearly distinguishes it from the sibling resimpli_remove_lead_from_automation, so an agent can route correctly without opening a schema.

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?

It gives some operational context ('By default you confirm each call; you can switch that off for this tool', 'confirm with the user before each call'), which implies usage conditions. However, it never states when to choose this tool over alternatives such as removing a lead from an automation, so guidance stays implicit rather than explicit.

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