asin_reverse_traffic

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

The description indicates the tool performs a reverse lookup and cache coverage check, implying a read-only operation. However, with no annotations, it does not fully disclose whether the operation makes external calls, how the cache is checked, or any side effects. It gives some behavior but not complete transparency.

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?

The description is two short sentences with no filler. It front-loads the core purpose in the first sentence and then gives a clear usage trigger. Every word earns its place.

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 lack of output schema, annotations, and an unexplained second parameter, the description leaves significant gaps. It does not state what the tool returns (e.g., list of keywords, coverage percentage) or explain max_pages, making it incomplete for an agent to use confidently.

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 0%, so the description must compensate. It references the ASIN parameter implicitly by saying 'for an ASIN,' but provides no explanation for 'max_pages.' The description adds minimal meaning beyond the schema and leaves one parameter entirely unexplained.

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 a specific action: 'Reverse-lookup traffic keywords for an ASIN' and adds the secondary purpose 'check cache coverage.' This distinguishes it from siblings like asin_score or keyword_analyze, which operate in the opposite direction or on different resources.

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?

Provides an explicit usage trigger: 'USE THIS TOOL WHEN: Checking if an existing product's keywords are covered by the ABA cache.' This gives clear context for when to use the tool, though it does not mention when not to use it or name alternative tools.

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