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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds nothing to explain cost, latency, quota, or what the call returns. Notably, a keyword lookup is intuitively a read operation while the annotation says otherwise, and the description does nothing to reconcile or add context on that point.

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 with no filler, but the brevity reflects under-specification rather than economy — the single fragment carries no actionable content beyond the title.

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 13-parameter research tool with no output schema, the description supplies no information about result shape, pagination behavior (needCount triggers internal automatic pagination), or the sort-field table referenced by the schema. It is completely inadequate for the tool's complexity.

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 13 parameters (asins, marketplace, word-count and search-volume filters, sorting, needCount) are already documented in the schema. The description contributes no additional semantics, so the baseline of 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 description is essentially a restatement of the tool name/title ('Amazon Research JS: keywords/by asin API'), with no verb and no explanation of what the returned data represents. It hints at the resource (keywords keyed by ASIN) but gives no basis for distinguishing it from close siblings such as nexscope_data_sf_asin_keywords, nexscope_amazon_asin_keywords, or nexscope_data_js_keywords_by_keyword.

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 when-to-use guidance, no mention of the sibling keyword tools, and no stated conditions or prerequisites. An agent must infer everything from the parameter names alone.

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