keywords_by_asin

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds that keywords 'drive traffic' which is behavioral context, but does not explain other traits like pagination, rate limits, or response format. Bar is lowered by annotations, so a 3 is appropriate.

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?

A single, front-loaded sentence that is concise and immediately conveys the tool's purpose. Every word earns its place, but it could be slightly more informative without being verbose.

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?

Given the absence of an output schema, the description should explain what the tool returns (e.g., list of keywords with metrics, format, array objects). It only says 'discover which keywords drive traffic' without specifying the output structure, leaving the agent with incomplete context about the response.

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 coverage is 100%, so the schema already documents all three parameters with descriptions for asin, page_size, and marketplace. The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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 clearly states the tool discovers keywords that drive traffic to a specific Amazon listing via ASIN. It uses a specific verb ('discover') and resource ('keywords') and implies non-overlap with siblings like 'keyword_search_volume' which focuses on volume rather than traffic drivers.

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?

The description implies use for analyzing which keywords bring traffic to an ASIN but provides no explicit guidance on when to use versus alternatives like 'product_database_query' or 'sales_estimates'. The context signal of sibling tools is present but the description itself lacks differentiation.

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