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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and external-data reach are covered. The description adds the useful scoping fact that it works on any ASIN across multiple marketplaces and that it returns curve-style history, but says nothing about data freshness, sampling granularity, rate limits, or what happens when no history exists for an ASIN.

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 purpose sentence is well front-loaded, but the second sentence is a ~15-item keyword dump that largely restates what the first sentence already enumerated, followed by a redundant clause about triggering without explicit mentions. The bulk is trigger-spam rather than information, and nothing about return structure or limits earns space instead.

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?

With 12 parameters and no output schema, the description should orient the agent on the shape of the response (per-curve series, time buckets, units) or on cost/latency, none of which appear. It does adequately cover what domains of data are available and the marketplace scope, which is the minimum needed to call it correctly, but the omission of any result-shape context leaves a real gap for a data-heavy tool.

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%, so all 12 parameters — asin, domain with its enumerated marketplace IDs, days, and the show* curve switches — are fully documented in the schema itself. The description adds no syntax, unit, or default guidance beyond that, so baseline 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?

The first sentence uses a specific verb ('Query') with a precise resource ('Amazon product historical time-series data') and enumerates the returned dimensions (price, BSR, rating, seller count, sales) plus multi-marketplace ASIN scope. It is clear what the tool does, but it never distinguishes itself from the closely named sibling nexscope_amazon_product_history, leaving an agent to guess which historical tool to pick.

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 trigger list gives concrete user phrasings that should select this tool ('price history', 'BSR trends', 'Buy Box price trends') and explicitly extends coverage to cases where the user does not mention Nexscope or time-series. That is clear when-to-use context, but there is no when-not guidance and no stated alternative for overlapping siblings such as nexscope_amazon_product_history or nexscope_amazon_product_detail.

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