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

Annotations already flag destructiveHint=true and idempotentHint=false. The description goes further by enumerating exactly which entry states are cancelled (waiting, event-waiting, pending-review) and disclosing that processing or sent work cannot be recalled and is reported separately, which is genuinely useful beyond the structured fields.

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, zero filler, and the operation type is front-loaded before the state-level detail. Every clause earns its place.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description supplies the cancellation scope and irreversibility caveat, leaving only minor gaps around nodeId format and permission prerequisites.

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 67%: workspaceId and confirmed are self-documented in the schema, and nodeId has no description at all. The description adds only the indirect hint that the node is a single unit of work; it does not explain nodeId format or how workspaceId omission behaves. Baseline 3 given the schema already carries most parameter meaning.

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+resource combination ("cancel" on "leads" for "one workflow node") and scopes it to a single node. An agent can distinguish it from broader siblings like campaignstack_delete_workflow or campaignstack_retry_workflow_entries, though no sibling is named explicitly.

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 "Confirmed drain operation" implies when this is appropriate, and the note that processing/sent work cannot be recalled sets a boundary. However, it never states when to prefer this over retry_workflow_entries or delete_workflow, so usage is inferred rather than guided.

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