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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that – no mention of rate limits, pagination behavior, data freshness, or the fact that only one ASIN may be queried per call (which only appears in the schema).

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 a single short sentence, but brevity here reflects under-specification rather than economy – there is no front-loaded purpose statement, scope, or usage cue. Nothing in the sentence earns its place beyond echoing 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 10-parameter analytical query tool with no output schema, the agent needs to know what the results represent (keyword list with rank/search-volume metrics over a time slice) and how the time-slice parameters interact. The description supplies none of this, leaving the complex parameter surface unexplained.

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 reported at 100%, so all 10 parameters are already documented in the input schema, establishing a baseline of 3. The description contributes no additional parameter meaning, but it is not required to given the schema's completeness.

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 title almost verbatim ('Amazon Search Intelligence SF: asin Keywords API'), which is a tautology rather than a statement of what the tool does. It implies ASIN-based keyword data but never says it returns keywords associated with an ASIN, nor how that differs from siblings like nexscope_amazon_asin_keywords or nexscope_data_sf_keyword_overview.

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 guidance on when to use this tool, when to prefer an alternative, or what prerequisites exist. With ~10 near-duplicate ASIN/keyword tools in the sibling list, the absence of any routing guidance leaves the agent to guess.

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