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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description usefully adds that existing Amazon Ads authorization is reused and that downloads are token-based. However, "Create once" sits awkwardly in a read-only download tool and can mislead an agent into thinking this call creates a report, and nothing is said about token expiry or what the download actually returns.

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?

Only two sentences and no padding, but the front-loaded sentence is about auth/tokenization rather than the tool's action, and the second sentence describes a multi-tool workflow instead of this tool's own behavior. Information density is fine; placement is not.

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?

There is no output schema, so the description should clarify what a successful download yields (a file, a URL, base64 payload?) and whether the token is single-use or time-limited. Neither is addressed, leaving a small but critical gap for actually invoking and consuming the result.

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 0% for both parameters, so the description must carry the burden. It only hints at what documentToken is (obtained from polling) and says nothing about connectionId — presumably the Amazon Ads connection/authorization identifier — leaving an agent to guess its meaning and constraints.

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 a verb (download) and the key input (documentToken), but never states plainly that the output is the Amazon Ads Sponsored Products insights report file. The first sentence is about authorization plumbing rather than the action, so an agent must infer purpose largely from the tool name/title.

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?

"Create once, poll by reportId, then download using a documentToken" gives a clear three-step ordering and implies this tool is the last step, requiring a token obtained from the polling step. It stops short of naming the sibling tools (e.g. nexscope_amazon_ads_sp_insights_report_status) or stating what to do when the token is missing/expired.

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