schedule_campaign

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

No annotations provided, but description fully compensates by disclosing authentication via API key, Mailchimp rate limits, read-only/dry-run mode respect, rounding behavior, and required future time. Also describes error conditions.

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: opening sentence, usage guidelines, authentication/rate limits, parameter docs, output description, example. Every sentence adds value with no redundancy.

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 prerequisites, behavioral details, error conditions, return values, and includes an example. With no annotations, the description leaves no gaps for an AI agent to invoke 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?

Input schema has 0% coverage, but description provides detailed semantics: campaign_id includes example and status condition, schedule_time includes ISO 8601 format, minimum 15 minutes future, and quarter-hour rounding.

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 'Schedule a campaign draft for sending at a specific future time,' using a specific verb and resource. It distinguishes from siblings like unschedule_campaign, send_campaign, and send_test_email.

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 (schedule delivery of a draft campaign), prerequisites (must have content set via set_campaign_content and be in 'save' status), and alternatives (unschedule_campaign, send_campaign, send_test_email).

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