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

Annotations already flag destructiveHint=true and openWorldHint=true, yet the description still adds real value: sending is timed and unattended, and the server performs no human-confirmation check, so the caller owns that gate. It stops short of saying whether activation is reversible or what happens to leads already mid-sequence.

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?

Two sentences, both earning their place: the first defines the action and effect, the second escalates the risk. The consequence is front-loaded with zero filler.

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 destructive, no-output-schema mutation, the description supplies the key operational facts: emails will go out on a timer and no human-confirmation check exists server-side. The remaining gap is failure/reversal behavior for `sequenceId` (non-draft sequences, idempotency).

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 coverage is 50%: `project` is documented in the schema, but the required `sequenceId` has no description anywhere. The description mentions no parameters at all, so it fails to compensate for the undocumented required field (e.g., that it must reference a draft rather than an active sequence).

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?

"Activate a draft sequence" states a specific verb and resource plus the state transition (draft → active) and the downstream effect on lead enrollment. It is clear on its own, but it never names the inverse (pause_sequence) or the creator (draft_sequence) as siblings, so explicit differentiation is left to inference.

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 phrase "so future matching leads are enrolled and may receive its emails" gives the agent the condition that makes this the right call, and the human-confirmation note signals a prerequisite to check first. There is no explicit when-not-to-use guidance or named alternative (e.g., pause_sequence to reverse it).

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