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

The description discloses the timing (~30s worker tick), that it overrides the schedule, and that the schedule continues normally afterward. This adds context beyond the annotations, which already indicate a non-read-only, non-idempotent operation. The description doesn't contradict 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 concise sentences that front-load the action and provide immediate details on timing and subsequent schedule behavior. No unnecessary words.

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 simple one-parameter tool without output schema, the description covers the purpose, timing, and schedule recovery. It could potentially mention prerequisites like the campaign being paced/active, but the phrase 'paced list campaign' implies that.

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?

The schema covers the single 'id' parameter fully with a description, and the description doesn't add additional semantic detail about the parameter. The behavior of feeding the campaign ID is implied by 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?

The description clearly states the tool fires the next batch of a paced list campaign immediately, using specific verbs ('Fire') and identifying the resource (list campaign). It distinguishes from sibling tools like pause/resume/update by focusing on the immediate run action.

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 provides clear context for when to use it (to trigger the next batch now, regardless of schedule). However, it does not explicitly name alternatives or state when not to use it, though the sibling list suggests related campaign actions.

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