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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description supplies zero behavior context to supplement them — no mention of data freshness, quota/rate limits, cost, or what the query is scoped to. For a 10-parameter open-world data query, the description carries no behavioral information at all.

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, so nothing is bloated, but it is under-specified rather than concise — there is no substantive content to front-load. It occupies the description slot without earning it.

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 10 parameters, an open-world data source, and no output schema, the description should at minimum say what the response contains (keyword rows with rank/search-volume fields) and what data source 'SF' represents. All of that is missing, leaving only the schema to guide correct invocation.

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 every parameter including `conditions`, `sortBy`, and `timePieceType` is documented in the schema itself. The description adds nothing beyond that, which is the baseline case when the schema does the heavy lifting.

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 and tool name ('Amazon Search Intelligence SF: asin Keywords API') without adding a verb-level statement of what is returned. An agent can infer that it fetches keywords associated with an ASIN, but only from the name and the required `asin` parameter, not from the description.

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 or when-not-to-use guidance, and no routing to alternatives. The sibling list contains near-duplicates such as nexscope_amazon_asin_keywords, nexscope_data_js_keywords_by_asin, and nexscope_data_sf_asin_summary, and the description gives no basis for choosing among them.

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