resend_to_non_openers

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

Without annotations, the description discloses non-idempotency, rate limits, auth method, dry-run support, and error conditions. Fully transparent.

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 informative and well-structured, though somewhat verbose. It front-loads the main action and uses clear sections.

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's complexity and no annotations, the description covers prerequisites, workflow, constraints, and return values. An output schema exists to further clarify returns.

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 only parameter 'campaign_id' is described with an example and source recommendation, adding value beyond the schema's minimal title and type. Schema coverage is 0%, so description compensates well.

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 it creates a new draft campaign targeting non-openers with inherited content. This distinguishes it 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 workflow and cautions against using with A/B test campaigns or campaigns sent less than 24 hours. Does not explicitly name alternative tools, but the context is clear.

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