create_campaign

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

The description adds the key behavior that creation does not send, which is valuable beyond the minimal annotations. However, this claim ('never sends') may contradict the scheduled_at parameter, which is described in the schema as scheduling the send. The description does not mention scheduled_at or any exceptions, making the behavioral disclosure slightly misleading.

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 two sentences, front-loaded with the main purpose, and each sentence provides essential information. No word is wasted.

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?

The tool has 11 parameters and no output schema, yet the description does not mention what the response contains (e.g., campaign ID) or any prerequisites like verified sender. The draft/send distinction is covered, but a create operation with this complexity would benefit from more context about return values or setup requirements.

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 description coverage is 100%, so all parameters have detailed descriptions in the schema. The description itself adds no parameter-level semantics, so it meets the baseline of 3 but does not exceed it.

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 verb ('Create'), the resource ('new email marketing campaign'), and the state ('as a draft'). It explicitly distinguishes from send_campaign by noting that creation never sends, making the tool's purpose unambiguous.

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?

It explicitly instructs to call send_campaign separately after content and audience are confirmed, providing a clear when-to-use and when-to-use-alternative. The statement 'Creating never sends' establishes the boundary between creation and sending.

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