schedule_campaign

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

With no annotations, description carries full burden but only states the core action. Does not disclose necessary authentication, mutability, consequences (e.g., campaign state change), or if sending is irreversible. Minimal behavioral context beyond the verb.

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?

Single sentence, front-loaded with purpose, no redundant words. Efficiently conveys core functionality.

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?

No output schema or return value description. For a sending/scheduling tool, outcome (success, scheduled time, errors) is missing. Incomplete for an agent to fully understand tool behavior without trying it.

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?

Description adds meaning beyond schema by clarifying that campaign must be a draft and that one target type (audience/segment/topic) must be chosen. Schema covers 50% of parameters; description compensates for undocumented target IDs.

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?

Description clearly states the action (schedule/send), resource (existing draft campaign), and target (audience/segment/topic). Verb+resource+scope is specific and distinguishes from siblings like pause_campaign or resume_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?

Description implies usage for scheduling or immediate sending of a draft campaign, but lacks explicit when-to-use vs alternatives like send_broadcast or send_campaign_test. No exclusions or guidance on choosing between options.

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