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

Annotations already declare idempotent=true and destructive=false, covering safety behavior. The description adds one piece of contextual behavior: the campaign must be paused before resuming. It does not describe side effects, errors on invalid state, or authorization requirements, but for a simple state-transition tool with solid annotations this is adequate.

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?

A single, front-loaded sentence with no wasted words. It states the action, the object, and the required prerequisite ('paused') in one breath.

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 tool with a fully documented schema and non-destructive/idempotent annotations, the description is sufficiently complete. It could add explicit contrast with sibling resume tools, but nothing required to make the call is missing.

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 campaignId parameter is already fully documented as a UUID of the paused SMS campaign. The description adds no further parameter-level meaning or guidance beyond what the schema already states.

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?

The description uses a specific verb ('Resume') and a specific resource ('paused drip SMS campaign'), which clearly distinguishes it from siblings like neuron_resume_campaign and neuron_resume_list_campaign. The resource qualifier makes the tool's scope unambiguous even without opening the 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?

The description implies the usage condition by including 'paused' – the tool is meant for campaigns currently in a paused state. However, it does not explicitly mention alternatives or when-not-to-use, such as steering non-drip or other campaign types to neuron_resume_campaign. Guidance is implied, not stated.

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