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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a dangerous write path. The description adds genuine value beyond that: credentials stay server-side (no token handling by the caller) and mutations must be previewed then confirmed. It still does not say what is destroyed or which entity types the mutations touch, so it is useful but not rich.

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?

Four short sentences, roughly 20 words, with the security/confirmation facts up front and no filler. The first sentence is redundant with the title, which is the only real waste.

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?

The schema is rich and fully documented and there is no output schema to explain, so much of the burden is carried. But for a destructive, open-world pass-through with 11 params, the description omits what the tool actually does to SP campaigns and how it differs from its near-duplicate siblings.

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% and the 11 parameters are documented in detail (method POST/PUT, nextToken vs startIndex paging, contentType, confirmationToken workflow). The description contributes nothing parameter-specific, so the baseline of 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?

"Amazon Ads: sp/campaigns API" restates the name and title rather than stating a verb+outcome; the only additional semantics are that it is a credential-proxied call and that mutations exist. With siblings like nexscope_data_amazon_ads_developer_proxy_sp_campaigns_list, sp_campaig_5eee0ed48e3b, sp_campaig_815253c43220, sb_campaigns and sd_campaigns, an agent cannot tell which of these handles create/update of SP campaigns versus list/read.

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 statement of when to use this rather than the many sibling SP/SB/SD campaign tools, and no prerequisites beyond a vague "Uses your Nexscope Amazon Ads connection." The only usage-adjacent content is the preview-then-confirm note for mutations, which describes a protocol rather than a selection criterion.

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