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

Annotations already declare non-read-only, idempotent, non-destructive behavior. The description adds genuinely new context: already-enrolled contacts remain enrolled but stop advancing until reactivation, and only active sequences qualify. It omits what happens to in-flight sends or the response shape, but the state semantics disclosed are valuable.

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 short sentences, zero filler, and the core action is front-loaded ahead of the caveats. Every sentence earns its place by adding either scope or a precondition.

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 one-parameter mutation with no output schema, the description covers action, side effects on enrolled contacts, and the validity precondition. Missing only edge-case behavior (e.g., what happens to pending sends) and any mention of reactivation via the sibling tool.

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?

There is a single parameter (sequence_id) with 100% schema description coverage, so the schema already carries the meaning. The description adds nothing about the parameter, which is the expected baseline when the schema does the work.

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 ('Pause') and resource ('an active sequence') plus the operational effect ('stops processing enrollments'). An agent can distinguish it from meisa_activate_sequence, meisa_pause_broadcast, and meisa_update_sequence without opening any 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?

Gives a clear precondition: 'Only active sequences can be paused,' which tells the agent when the call is valid. It does not explicitly name the counterpart tool (meisa_activate_sequence) or state what to do when the sequence is not active, so it stops short of full routing guidance.

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