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

Annotations already declare this as a non-read-only, destructive, open-world mutation. The description adds the DRAFT-campaign scope, which is useful context, but does not explain overwrite behavior, validation failure modes, required permissions, or what exactly gets destroyed when conversion actions are replaced (the schema notes replacement, not the description).

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 states the action, target, and affected settings with no filler. Every clause corresponds to a parameter group, so no sentence is wasted.

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 fully described schema, mutation annotations, and absence of an output schema, the description supplies enough context to identify the tool and its DRAFT-only scope. It could be slightly richer about post-update behavior or prerequisites, but it is largely complete for 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?

Schema description coverage is 100%, so the schema already documents all six parameters in detail, including enum constraints and side effects like resetting the bidding goal. The description mostly mirrors those fields and adds little semantic detail beyond what the schema provides.

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 uses a specific verb ('Update') and resource ('LinkedIn channel settings'), and scopes it to an 'existing DRAFT wizard campaign.' It clearly enumerates the settings affected, making the purpose unambiguous, though it does not explicitly name or differentiate against sibling tools such as update_reddit_channel_settings or manage_campaign.

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 'existing DRAFT wizard campaign' phrase implies usage context and implicitly excludes live or non-LinkedIn campaigns. However, there is no explicit when-to-use guidance, no stated exclusions, and no pointer to alternatives for live campaign updates.

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