wafle_ads_bulk_pause

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

Annotations already indicate idempotent and destructive hints. The description adds valuable behavioral details: partial success visibility (per-id success/failure) and a 1 RPS throttle to respect Meta's rate limit. No contradiction with 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?

Three sentences, each earning its place: purpose, return behavior, and usage context. Front-loaded with the action, no filler.

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?

Despite lacking an output schema, the description explains the return format (per-id success/failure). It covers purpose, use cases, behavior, and throttling, making the tool fully understandable for its complexity.

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%, and both parameters (slug, campaign_ids) are well-described in the schema. The description reinforces the bulk nature but adds no new parameter-specific semantics 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 clearly states the verb and resource: 'Pause many Meta campaigns in a single tool call.' It distinguishes itself from siblings like wafle_ads_campaign_pause by emphasizing the bulk nature and per-id success/failure reporting.

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?

Explicitly provides use cases: 'Best for ROAS-floor sweeps... and seasonal cleanup.' It also notes the backend throttling behavior, helping agents decide when this tool is appropriate. However, it does not explicitly contrast with the single-campaign pause sibling.

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