amazon_product

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

No annotations are provided, so the description carries full burden for behavioral traits. It discloses the output contents (FBA fee, profit margin, opportunity tier) but does not mention any side effects, rate limits, data freshness, or external calls. Additional context would improve 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?

A single sentence that front-loads the core purpose and lists key outputs. No wasted words, highly efficient.

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 there is no output schema, the description gives a good sense of what the tool returns (FBA fee, profit margin, opportunity tier). It covers the single-product analysis scope adequately. Could mention that the output is a detailed report, but overall complete enough.

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 the baseline is 3. The description does not add significant meaning beyond the schema; it mentions 'by ASIN' which matches the asin parameter, but does not elaborate on the marketplace parameter or provide formatting hints.

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 it performs 'deep analysis of a single Amazon product by ASIN' and lists specific outputs (FBA fee estimate, profit margin, opportunity tier). This distinguishes it from siblings like amazon_search, which is for searching products.

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 the tool is for analyzing a single product in depth, but does not explicitly state when to use it versus alternatives (e.g., amazon_search for broader queries). It provides context for use but lacks explicit guidance.

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