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

With no annotations supplied, the description carries the full burden and does well: it flags `add` as the highest-risk call, discloses the BYO-key/credential requirement, notes dry_run only echoes the request (no get-by-id diff), and clarifies that `per_page` is a most-recent window rather than pagination. However it contradicts itself on credentials — the intro says `activity` accepts the platform key while the `activity` bullet says 'BYO key only' — leaving the agent unsure which key that op needs.

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 structure is disciplined — a one-line scope statement followed by one bullet per op, with required args and warnings inline. It is dense but every line carries operational content; the risk warning for `add` would land harder if front-loaded rather than embedded mid-bullet.

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 17-parameter, no-output-schema, no-annotation mutation tool, this is a solid briefing: it covers risk, credentials, dry_run semantics and per-op required args. Gaps remain — no statement of what `add` or `activity` returns, an unexplained `status` parameter, and the unresolved credential contradiction for `activity`.

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 (29%) across 17 params, so the description must compensate, and it largely does: it maps sequence_id, send_email_from_email_account_id, contact_ids, label_names, emailer_campaign_ids, mode, contact_id, per_page and dry_run to specific ops and states which are required. It leaves `status`, `send_email_from_email_address` and the `_org`/`_group`/`_project`/`_instance`/`_run_id` routing params undiscussed from the op perspective.

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 opening sentence names a specific resource (contacts in Apollo sequences) and three distinct operations (enroll/update/inspect), and the per-op bullets decompose each into concrete args. An agent can immediately tell this apart from apollo_sequence or lemlist_sequence tooling.

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 explicit per-op prerequisites (e.g. `add` requires a CONNECTED mailbox id obtainable from apollo_email_accounts, plus contact_ids or label_names), warns that `add` starts a multi-step campaign rather than a single send, and notes dry_run availability per op. It stops short of telling the agent when to prefer a sibling tool or when to use `stop` vs `remove` in `update_status`.

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