update_campaign

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Update', which implies mutation, but does not disclose permissions, idempotency, partial vs full update behavior, or error conditions. This is insufficient for a mutation tool.

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 a single sentence with no fluff. It is concisely front-loaded with the action and resource, efficiently listing the modifiable aspects.

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, no output schema, and no annotations, the description is too brief. It does not address return values, behavior on non-draft campaigns, validation, or potential side effects, leaving significant gaps for safe invocation.

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?

The description adds meaning by grouping parameters into 'content, subject, preview text, or sender info', which covers most but not all parameters (apiKey, campaignId, templateSlug are not mentioned). However, given 22% schema description coverage, the description partially compensates but remains vague.

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 'update' and the resource 'campaign', listing specific fields (content, subject, preview text, sender info) that can be updated. It distinguishes from sibling tools like delete_campaign or pause_campaign, but does not clarify if the 'draft' status is enforced by the tool.

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 guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or constraints mentioned. The description lacks information about when not to use it, such as for sent or scheduled campaigns.

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