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

Beyond the annotations (readOnly, openWorld, non-destructive), the description adds real behavioral context: an async 'one submit and at most eight fixed reads' pattern, the warning that missing values are not zero, that prices/publication are unapproved, and that completed results persist in owner call history. The phrasing is cryptic in places ('source-bound', freshness dependency), which keeps it from a 5.

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?

It is short and front-loads the resource, but several sentences are compressed into jargon ('source-bound', 'eight fixed reads', 'dependent requests') that trades clarity for brevity rather than earning its place through precision.

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 read-only retrieval tool with annotations covering the safety profile and no output schema required, the behavioral caveats are useful. However, the lack of any parameter explanation and no guidance on the async submit/read lifecycle leaves real gaps an agent must guess around.

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?

With 3 parameters at 0% schema description coverage, the description must explain task_id, productRef (a 64-hex hash), and limit. It mentions none of them, leaving the opaque hash reference entirely undefined to the agent.

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?

It names the resource (Google Shopping seller offers) and hints at the output (observed prices, missing evidence), but never states a clear verb like 'retrieve' or 'list', and never differentiates itself from close siblings such as nexscope_seo_shopping_products or nexscope_seo_shopping_product_details. An agent can infer the domain but not the precise action or its boundary.

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?

There is no explicit when-to-use, when-not-to-use, or alternative routing. The 'seven-day source-freshness rules apply only to dependent requests' line is a constraint, not usage guidance, and it presumes knowledge the agent doesn't have.

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