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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false. The description adds meaningful non-annotation context: both active and paused enrollments are exited, the contact stops receiving steps, the reason is optional metadata, and a non-enrolled contact produces an error.

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?

Four tight sentences, front-loaded with the action and scope, then the identifying parameters, the effect, and the error condition. No filler or repetition.

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?

No output schema exists, and the description covers the notable return behavior (error when not enrolled) plus the state transitions affected. It stops just short of describing any success payload, but for a three-parameter mutation this is close to complete.

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%, so the schema already documents email, sequence_slug and reason. The description largely restates the schema (slug from meisa_list_sequences, optional reason) without adding format/syntax detail, so the baseline of 3 is appropriate.

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?

Specific verb (remove/unenroll) plus resource (contact from a sequence) with explicit scope: 'exiting their active or paused enrollment'. This clearly distinguishes it from the sibling meisa_enroll_in_sequence and the various pause/resume sequence tools.

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?

Explains the identifying keys (email + sequence slug) and the precondition that the contact must currently be enrolled, and states the effect ('stops receiving further steps'). It does not explicitly name pause_sequence or delete_sequence as alternatives, so the boundary with sibling tools is implied rather than stated.

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