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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the destructive profile is covered. The description adds that credentials stay server-side (genuine security context), but the preview/confirm workflow it mentions is already spelled out in the `confirmationToken` parameter description, so the added value is limited.

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 short, front-loaded sentences with no filler. The first sentence is wasted duplication of the title, but the remainder is efficient and the mutation caveat is placed where an agent will see it.

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?

This is a destructive, open-world proxy to a complex upstream API with 12 parameters and no output schema, yet the description never says which SB campaign operations/entities are reachable, what a response looks like, or how paging interacts with the mutating methods. Against a sibling list containing a dozen overlapping SB/SD/SP campaign tools, this is not enough to call it correctly with confidence.

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?

With schema description coverage at 100% across all 12 parameters (including `method`, `accept`, `fetchAll`, `confirmationToken`), the schema already carries parameter semantics. The description contributes nothing additional about any parameter, so baseline 3 applies.

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 first sentence repeats the title verbatim ('Amazon Ads: sb/campaigns API'), naming a resource surface but no verb — the actual operation depends on the `method` parameter. It does not distinguish this tool from near-identical siblings such as `..._sb_v4_campaigns`, `..._sb_v4_campaigns_list`, `..._sd_campaigns`, or `..._sp_campaigns`, all of which an agent must choose between.

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 only usage signal is 'Mutations require preview and confirmation', which is a workflow constraint rather than a when-to-use rule. There is no statement of what this endpoint is for versus the v4/list/SD/SP campaign tools, and no read-vs-write guidance despite `method` driving behavior.

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