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

The annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known; the description adds two non-redundant facts — credentials stay server-side and mutations go through a two-step preview/confirmation token. It does not say which operations are destructive, what gets removed, or what the upstream response looks like.

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 with no filler, and the identifying information plus the mutation workflow caveat are front-loaded. Slightly under-informative rather than bloated, so no waste to trim.

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?

For an 11-parameter destructive open-world proxy with no output schema, the description leaves major gaps: no indication of the entity shape, no note on what a successful mutation returns, and no differentiation from the extended variant — the agent cannot tell when this endpoint family is the right call.

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 schema itself documents `method` semantics (GET/POST/PUT), `fetchAll`, `maxResults`, and `confirmationToken` thoroughly. The description adds nothing beyond the schema, so the 3 baseline 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 description names the resource (Amazon Ads sd/campaigns endpoint) but supplies no verb and no indication of what the tool actually does with it — list, create, or modify — leaving the agent to infer purpose from the `method` parameter. It also fails to distinguish this tool from the close sibling `nexscope_data_amazon_ads_developer_proxy_sd_campaigns_extended`.

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 guidance is the workflow rule that mutations require preview and confirmation. Nothing tells the agent when to pick this tool over the SD extended variant, the SP/SB campaign proxies, or the higher-level `nexscope_amazon_ads_manager`/`nexscope_amazon_advertising` tools.

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