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 by structured data. The description adds nothing beyond that — no indication of data source, freshness (the last7d default), rate limits, or what an 'overview' contains versus a 'summary'.

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 only one short sentence, so nothing is wasted, but it is under-specified rather than concise — it conveys no information an agent could act on. The front-loaded material is just the title repeated.

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?

With five parameters, no output schema, and dozens of overlapping keyword tools, the description should explain what the overview response contains and how it differs from the sibling SF keyword tools. It does none of that; only annotations and the schema carry any weight.

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 five parameters (keyword, country, last7d, startDate, endDate) are documented in the schema itself. The description contributes no additional semantic meaning, but per the high-coverage baseline a 3 is the appropriate floor.

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 restatement of the tool name/title ("Amazon Search Intelligence SF: keyword Overview API") with no verb describing an action and no statement of what data is actually returned. It also does not differentiate from near-identical siblings such as nexscope_data_sf_keyword_summary or nexscope_amazon_keyword_overview. An agent can only guess from the token "keyword" that this is keyword-metric retrieval.

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 exclusions, and no reference to any of the many alternative keyword tools in the sibling list. The agent has to infer usage entirely from the country/date parameters.

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