apollo_add_contacts_to_sequence

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

Without annotations, the description should disclose behavioral traits like side effects, prerequisites, or error conditions. It only states the action without explaining what happens when contacts are added, whether it's idempotent, or if permissions are needed. This is insufficient for safe usage.

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 at one sentence plus a note, but it is too brief given the tool has 8 parameters. It sacrifices completeness for brevity, making it less useful than it could be.

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?

With 8 parameters, no annotations, and a brief description, the tool is underdescribed. The output schema exists but does not compensate for the lack of behavioral context. The description does not cover typical use cases, prerequisites, or outcomes.

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 low (38%). The description adds value for one parameter (send_email_from_email_account_id) by noting it is typically required, but the other 5 parameters lack any description in both schema and description, leaving their semantics unclear.

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 'Add one or more contact IDs to an emailer sequence', using a specific verb and resource. However, it does not differentiate from sibling tools like remove_contacts_from_sequence or abort_sequence, which limits distinction.

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 mentions that send_email_from_email_account_id is typically required, giving some usage guidance. But it does not provide context on when to use this tool versus alternatives (e.g., remove or abort), nor exclusions.

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