create_campaign

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

No annotations are provided, so the description carries the full burden. It describes the tool as creating a campaign, implying a write operation, but does not disclose side effects, authentication requirements, rate limits, or return value structure. The presence of an output schema is not referenced.

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 very concise at two sentences. The first sentence states the purpose, the second lists campaign types. While efficient, it could benefit from structured formatting (e.g., bullet points for parameters) but remains clear and not verbose.

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?

Given 8 parameters (6 required) and no parameter descriptions, the description is incomplete. It does not explain required fields, format expectations, or relationship to other tools like send_campaign. The output schema exists but is not mentioned.

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%, so the description must compensate. It only adds meaning for campaign_type by listing valid values. The other 7 parameters (name, list_id, subject, etc.) are left unexplained, leaving the agent without guidance on their format or constraints.

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 'Create a new email campaign' with the specific resource 'campaign'. Listing campaign types adds detail. It is distinct from sibling tools like create_contact or create_deal which target different entities.

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?

No explicit guidance on when to use this tool vs alternatives. The context of sibling tools suggests creation is for new campaigns, but no prerequisites or exclusions are mentioned. Usage is implied but not clarified.

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