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

The description adds real context beyond the annotations: it reuses existing Amazon Ads authorization and uses tokenized download handling, and the token flow implies the documentToken is single-use/obtained downstream. However, with readOnlyHint=false and no output schema, it fails to say what is actually produced (file, URL, bytes), whether the token expires, or what side effect justifies the non-read-only hint.

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?

Two short sentences with no filler, and the workflow sequence is compact. The first sentence, however, leads with implementation detail ('Uses existing... tokenized download handling') rather than the action, which buries the point.

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 a two-parameter terminal download tool with no output schema, the description should clarify the returned artifact and token lifetime. It covers the auth and token aspects but leaves the consumer without knowing what it receives or whether the token can be reused, which matters given readOnlyHint=false.

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 coverage is 0%, so the description must carry the parameter burden. It names documentToken and ties it to the download step, which is the key semantic, but never explains where the token comes from (the status poll) or what connectionId means beyond 'existing authorization', leaving connectionId entirely undocumented.

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 never states plainly that this tool downloads an Amazon Ads Sponsored Products Insights report; the verb 'download' appears only inside the workflow clause 'then download using a documentToken'. An agent must lean on the tool name and the sibling status tool to infer the resource. The scope (sp insights report) and the exact action are never in one clear statement.

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' gives sequencing context, implying this is the terminal step after nexscope_amazon_ads_sp_insights_report_status, but the alternatives are never named and there are no exclusions. The agent gets implied placement in a workflow rather than explicit guidance on when to choose this versus the reporting/status siblings.

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