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

The annotations already mark this as read-write, idempotent, and non-destructive. The description adds a meaningful state-machine constraint: only 'sending' drip campaigns can be paused. This helps the agent understand the precondition and likely error behavior without contradicting the annotations.

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 short sentences with no filler. The core action and the key state precondition are front-loaded, making it easy for an agent to scan and act on.

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 single-parameter mutation with strong annotations and full schema coverage, this is largely complete. It covers the main precondition (sending state) and identifies the exact resource type. It could mention what happens after pausing or how to resume, but that is not essential for correct invocation.

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 100% and campaignId is already described as 'UUID of the SMS campaign to pause'. The description reinforces that the target is a drip SMs campaign but does not add meaningful detail beyond the schema.

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'), resource ('SMS drip campaign'), and the exact state the resource must be in ('sending' state). This clearly distinguishes it from sibling tools like neuron_pause_campaign, neuron_pause_list_campaign, and neuron_pause_ad_request.

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 clear context for when this tool applies: only a drip SMs campaign currently in the 'sending' state. It implicitly excludes non-drip campaigns and non-sending states, though it does not explicitly name an alternative tool for those cases.

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