resend_to_non_openers

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

Discloses non-idempotency, required status 'sent', respect for read-only/dry-run modes, concurrency limit (10), authentication via API key, and error conditions. This compensates for lack of 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?

Very concise and structured: first sentence states main purpose, then bullet-like details on behavior, workflow, restrictions, and arguments. Every sentence provides value.

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?

Given the tool has one parameter, an output schema, and no annotations, the description fully covers purpose, parameters, return values, preconditions, and limitations. Complete for effective usage.

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?

Adds significant meaning to the single parameter 'campaign_id' with example format, source (list_campaigns(status='sent')), and purpose, beyond the minimal schema definition.

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 creates a new draft campaign targeting non-openers, specifying the verb 'create', the resource 'draft campaign', and the target audience. It distinguishes from siblings like 'create_campaign' and 'replicate_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?

Provides explicit guidance on when to use (original sent campaign), when not (A/B tests, campaigns <24h old), and a workflow sequence (resend_to_non_openers → update_campaign → send/schedule_campaign). Also mentions exclusions.

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