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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of result set nature, pagination limits, quota/credit cost, or what the summary rows represent, despite being an open-world data-pulling call.

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 line with no wasted words, but that brevity is under-specification rather than conciseness — the one sentence conveys no information not already in 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?

An 11-parameter analytics query tool with no output schema demands a description explaining what the summary contains and how filters/sort/paging combine. The description provides none of that, leaving the agent entirely dependent on the schema field names.

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 (searchKeyword, country, sortBy, condition, last7d, date range, paging) are already documented in the schema. Per the rubric this establishes a baseline of 3 regardless of the description, which contributes zero parameter guidance.

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 tool name and title ('Amazon Search Intelligence SF: keyword Summary API'), giving no verb that says what it actually does with the keyword. An agent cannot tell it apart from siblings like nexscope_data_sf_keyword_overview, nexscope_data_sf_asin_summary, or nexscope_amazon_keyword_summary.

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 statement of when to use this tool, when not to, or which sibling to prefer for an ASIN summary versus a keyword overview. The only implicit signal is the 'SF' prefix and 'keyword' noun, which is insufficient to route between the many Amazon keyword tools.

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