campaigns_create

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

With no annotations, the description carries the full burden but only states the create action and the 'outbound' type. It does not disclose side effects, required permissions, return behavior, or validation expectations, providing minimal transparency beyond the tool name.

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 one-sentence description is concise but severely under-specified for a tool with three required parameters and a nested object. It is not well-structured because it omits essential usage and parameter guidance, making it an under-specification rather than effective brevity.

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 operation with no annotations, no schema parameter descriptions, and a nested required object, the description is highly incomplete. It does not mention prerequisites, valid parameter values, or the campaign lifecycle, leaving most of the necessary operational context absent.

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 0%, and the description does not explain any of the three required parameters (name, connect_instance_id, channel_subtype_config). It also gives no insight into the nested channel_subtype_config object structure, leaving the agent unable to construct valid inputs.

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 uses a specific verb and resource ('create an outbound campaign'), which unambiguously states what the tool does. It also distinguishes this from sibling tools like campaigns_list and campaigns_start by focusing on the create action for campaigns.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or relationships to sibling tools like campaigns_start or campaigns_describe. There is no context at all beyond the one-sentence purpose.

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