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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds nothing on top of that: no note about the Amazon marketplace dependency, no indication of result volume, sorting behavior, or whether `needCount` changes the response shape. With annotations present the bar is lower, but zero added context still warrants a low score.

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 single sentence is short but vacuous — it is under-specification rather than conciseness. There is no front-loaded statement of what the call does or returns; every word duplicates 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?

This is a 12-parameter research API with two required inputs, no output schema, and no description of what a keyword result record contains. Given that complexity, a one-line title restatement leaves the agent unable to predict the response or the effect of the many filter parameters.

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 (including the required `marketplace` and `searchTerms`, the filter bounds, and `sort`) are documented in the schema itself. The description contributes no additional semantics, but the baseline of 3 applies because the schema carries the load.

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 restates the tool title almost verbatim ('Amazon Research JS: keywords/by keyword API') without a verb or statement of what is actually returned. An agent can infer it looks up keyword data for a seed term from the parameter names, but the description itself adds nothing beyond the name and does not distinguish it from sibling tools such as nexscope_data_js_keywords_by_asin or nexscope_data_js_keywords_share_of_voice.

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 prerequisites, and no routing to alternatives, despite a large family of closely-named JS keyword siblings. The agent must guess the distinction between by-keyword, by-ASIN, historical volume, and share-of-voice variants entirely from tool names.

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