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

The description adds meaningful behavioral context beyond the annotations: it emphasizes that this tool only creates a draft, cannot perform downstream actions, and uses a default 4-step sequence. This helps an agent avoid expecting side effects like sending or launching. No contradiction with 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?

Two sentences, front-loaded with the core action and scope, with no filler. Every sentence adds value, including the explicit draft-only warning and the follow-up dashboard link.

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?

For a create-draft tool with five parameters and no output schema, the description covers the essential behavior, the default sequence, and the next step. It does not specify behavior when both creator_ids and use_saved are provided, but this is a minor gap.

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?

Schema coverage is high at 80%, so the schema already documents most parameters. The description adds a helpful link between creator_ids and the saved-list workflow, but does not materially explain parameter semantics beyond what the schema already provides.

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 states a clear verb and resource: 'Create a DRAFT outreach campaign' from creator ids or a saved list. It also distinguishes itself from launch_campaign by explicitly saying it cannot launch, enroll, or send.

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?

The description clearly communicates when to use this tool ('DRAFT ONLY') and what it cannot do (launch, enroll, send). It points the user to the dashboard for launching, but does not explicitly name launch_campaign as the alternative tool, so the guidance is strong but not fully explicit.

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