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

The description adds context that existing Amazon Ads authorization and tokenized download handling are used, which is useful beyond the annotations. It does not clarify polling behavior, possible status values, or why readOnlyHint is false for what appears to be a status-check operation.

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?

The description is only two sentences and avoids filler. The auth sentence comes first, while the workflow sentence is compact but slightly confuses input reportId with the output-side documentToken.

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 status-polling endpoint with no output schema and no documented connectionId, the description is too thin. It does not explain what status information is returned, how pending or failed reports appear, or how connectionId should be obtained.

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%, so the description must compensate for both parameters. It mentions reportId in the polling workflow but does not explain connectionId at all, leaving a required parameter 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 implies polling a report by reportId, but never explicitly states that this tool retrieves the status of an SP Insights report. The name and title carry most of the purpose signal, while the description focuses on auth and workflow phrasing.

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?

It outlines a create-once, poll-by-reportId, then download-with-documentToken sequence, which gives implied usage context. However, it does not explicitly say when to use this versus the sibling nexscope_amazon_ads_sp_insights_report_download or what conditions indicate completion.

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