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

Annotations already flag destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description does add that existing content is replaced and supplies the underlying endpoint, which is useful, but it stays silent on constraints such as whether the campaign must already be a draft and whether the overwrite is recoverable.

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?

Two short clauses, front-loaded with the 'WRITE:' signal so an agent sees the mutation risk immediately. Nothing here is filler.

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 no output schema and only two well-documented parameters, the description covers the essentials: mutation type, effect on existing content, and endpoint. The remaining gap is the precondition that the target campaign must be a draft, which is only hinted at in the title.

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 coverage is 100%, so both required parameters (campaign_id, template_id) are fully documented in the schema, including id format constraints. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 and resource: load a saved template's content into a campaign, replacing existing content. It implicitly differentiates from sarbacane_set_campaign_content by framing the action as a template import, but it never names that sibling, so the distinction is left for the agent to infer.

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 title mentions 'draft campaign' and the description implies this is the template-based route to setting content, but there is no explicit when-to-use/when-not guidance and no mention of the directly competing sibling sarbacane_set_campaign_content.

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