androidapi_stop_wa_campaign

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

Annotations already indicate a non-destructive write operation (readOnlyHint=false, destructiveHint=false). The description adds no further behavioral context beyond 'pause,' such as whether the campaign can be resumed or any side effects.

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?

The description is extremely concise—one sentence of four words—with no extraneous information. It is front-loaded and directly states the tool's purpose.

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 pause tool with one parameter and no output schema, the description is largely complete. It could optionally mention that the campaign must be running or that the operation is reversible, but overall it suffices.

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%, so the schema fully documents the single parameter 'campaign' (Campaign ID). The description adds no additional meaning or usage context 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?

The description 'Pause a running WhatsApp campaign' uses a specific verb (pause) and resource (WhatsApp campaign), and clearly distinguishes this tool from siblings like 'androidapi_start_wa_campaign' and 'androidapi_delete_wa_campaign'.

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 usage (when a campaign is running) but provides no explicit guidance on when to use this tool versus alternatives, such as when to stop vs. pause, or how it differs from deletion.

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