resend_to_non_openers

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

Discloses non-idempotence: 'Not idempotent: calling twice creates two separate drafts.' and describes behavior like inheriting content and settings. This adds context beyond annotations (readOnlyHint=false, destructiveHint=true) 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?

Concise yet informative: first sentence states purpose, then covers idempotence, workflow, restrictions, error, and parameter details. No unnecessary words.

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: purpose, usage, behavior, and return values. Minor gap is the missing description for the 'account' parameter. Overall, sufficient for an AI agent to use correctly.

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?

Campaign_id is well explained with example and source. However, the optional 'account' parameter is not described at all. With 0% schema coverage, the description should explain all parameters but fails to do so for account.

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 purpose: 'Create a new draft campaign targeting only recipients who did not open the original.' This distinguishes it from siblings like create_campaign, replicate_campaign, etc., by specifying the targeting condition.

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: 'resend_to_non_openers -> update_campaign (change subject) -> send_campaign or schedule_campaign.' Also states when not to use: 'Do not use for A/B test campaigns or campaigns sent less than 24 hours ago.' and error condition: 'Returns error if the original campaign status is not sent.'

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