Create Campaign

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

Annotations indicate idempotentHint=true but description does not confirm idempotency; however, it describes auto-association of first active connection and default status=draft, adding value beyond annotations. No contradiction.

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?

Three sentences, each provides key information: purpose, process, and prerequisite. No filler. Could be slightly more concise by front-loading the action, but effective.

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 the tool has 9 parameters and no output schema, description covers input constraints (active connection, defaults to draft), return value (summary+next_steps), and prerequisite. Lacks mention of idempotency but annotations provide that. Sufficient for a creation tool.

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 89%, so parameters are well-documented in schema. Description adds context that parameters are 'unified' and that the tool stores a 'UnifiedCampaign record', but does not explain parameter details beyond schema.

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 it creates a new ad campaign in the AdOps workspace, accepts unified parameters, stores a UnifiedCampaign record with status=draft, and returns summary plus next_steps guidance. Distinct from sibling tools like campaign_update or campaign_pause_resume.

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?

Explicitly mentions requirement for an active platform connection and references platform_connect as prerequisite. Does not explicitly state when not to use (e.g., for updating existing campaigns), but context is clear.

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