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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description carries the full behavioral burden and delivers nothing: no indication of what data is returned, quota/credit consumption, auth requirements, or why a 'summary' endpoint is not read-only. No contradiction is asserted, but the disclosure gap is total.

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, but shortness here is under-specification rather than conciseness: a single sentence that duplicates the title earns no place and front-loads nothing actionable.

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 an 11-parameter Amazon search-intelligence query tool with no annotations beyond openWorldHint and no output schema, the description supplies none of the context an agent needs about the returned metrics, ranking behavior, or result shape.

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 11 parameters (country site list, sortBy fields, condition operators, date window, paging) are already documented in the schema. Per the high-coverage baseline, 3 applies even though the description adds no parameter meaning of its own.

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 a verbatim restatement of the title: 'Amazon Search Intelligence SF: keyword Summary API.' It implies a keyword-summary resource but names no verb describing what is actually returned or computed, and gives no way to distinguish it from siblings such as nexscope_amazon_keyword_summary 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 whatsoever on when to call this tool, when to prefer an alternative, or what prerequisites exist. With at least three similarly named keyword-summary siblings in the list, the agent has no basis for choosing this one.

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