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

Adds real information beyond the annotations: missing values must not be treated as zero, prices/publication are unapproved, results persist in owner call history, and there is a submit-plus-fixed-reads pattern that explains why readOnlyHint is false despite the tool being mostly a fetch. The async/task lifecycle (does task_id mean polling?) and the apparent mismatch between 'at most eight fixed reads' and the limit maximum of 10 are left unexplained.

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?

Purpose is front-loaded and the sentences are short, but heavy jargon ('source-bound', 'explicit missing evidence', 'dependent requests') costs clarity while contributing little actionable meaning. Some sentences earn their place (missing values are not zero), others are opaque filler.

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 no output schema, zero parameter documentation, and an unclear submit/read lifecycle, the description leaves too much for an agent to guess before a correct call. It covers data-quality caveats but not the mechanics of invoking or interpreting the 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 0% for three parameters, and the description never mentions task_id, productRef, or limit. The 64-hex productRef pattern and the role of task_id (identifier vs. idempotency token) are completely undocumented, and the 'eight reads' remark arguably conflicts with limit ≤ 10.

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?

States a specific resource — Google Shopping seller offers with observed prices for a product — which is more precise than the title alone. It does not, however, distinguish itself from the closely related siblings nexscope_seo_shopping_product_details and nexscope_seo_shopping_products, so an agent can't tell from the text alone which one returns offers vs. product metadata.

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?

No when-to-use, when-not-to-use, or alternative tool is named. Phrases like 'Seven-day source-freshness rules apply only to dependent requests' hint at preconditions but never state them in actionable terms, and there is no guidance on the relationship between task_id and productRef.

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