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

No annotations are provided, so the description carries the full disclosure burden and delivers almost none of it: it doesn't say the campaign is created active by default (is_active defaults true), that it will begin firing on live traffic immediately, whether it can be edited/deleted afterward, or what permissions/plan are required. For a side-effectful creation tool this is a substantial gap.

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?

A single front-loaded sentence with no filler, and the verb/resource lead. Its brevity is a deficiency in coverage rather than a structural flaw, but there is no structure to speak of beyond the one clause.

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?

With 9 parameters, zero schema descriptions, no annotations, and no output schema, the description should be doing heavy lifting and instead says nothing about configuration, defaults, or result. It is not remotely sufficient for an agent to call this correctly.

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% across 9 parameters, so the schema gives only bare titles and defaults. The description compensates for none of it — trigger_type, trigger_value, campaign_type, url_patterns, and target_devices are entirely unexplained, leaving the agent to guess accepted values and semantics.

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?

States a specific verb (Create) plus the resource (campaign) and qualifies the two modes — proactive announcement vs. visitor engagement. An agent can distinguish it from list_campaigns, update_campaign, and delete_campaign, though it doesn't clarify how it differs from the create_* siblings like create_webhook_subscription.

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?

There is no guidance on when to create a campaign versus other engagement mechanisms, no prerequisites (e.g. the bot_id must reference an existing chatbot), and no mention of related siblings such as update_campaign or get_campaign_analytics for follow-up. The agent must infer all of this from the name alone.

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