pause_rss_campaign

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

Description adds behavioral context beyond annotations: authentication via API key, max 10 concurrent requests, respect for read-only and dry-run modes. Annotations already indicate non-read-only, non-idempotent, non-destructive, and description aligns without contradiction.

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?

Well-structured: purpose first, usage guidelines, then arguments and returns. Every sentence is informative and necessary, no redundancy. Front-loaded with key action.

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?

Covers most aspects: type restriction, auth, rate limits, return format. However, does not mention idempotency behavior (e.g., pausing already paused campaign), which might be a gap given idempotentHint=false. Still, for a simple tool with output schema, it's nearly complete.

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?

With 0% schema coverage, description fully compensates: explains campaign_id source (list_campaigns or search_campaigns) and account usage including environment variable naming and default behavior. Adds significant meaning beyond schema titles.

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?

Clearly states the verb (pause), resource (RSS campaign), and effect (stops sending scheduled editions). Distinguishes from siblings like resume_rss_campaign and pause_automation by specifying it's for RSS campaigns only.

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 states when to use (temporarily halt RSS campaign), how to resume (resume_rss_campaign), prerequisites (confirm type with get_campaign_details), and authentication/rate limits. Provides clear context and alternatives.

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