keepa_get_buy_box

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

With no annotations provided, the description must disclose behavioral context. It partially does by specifying the output fields ('current seller, FBA status, and offers'), but it does not mention whether this is a pure read operation, any rate limits, or what happens when no buy box exists. The read-only nature is implied by 'Get' but not explicitly stated.

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, well-structured sentence conveys the tool's purpose and main output attributes without any filler or repetition. Every word adds value, making it easy to parse quickly.

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?

The tool is relatively simple (2 params, no output schema), and the description covers the core purpose and primary output fields. However, it lacks behavioral details such as whether multiple ASINs are processed individually or as a batch, and any edge-case behavior. Given no annotations or output schema, the description is adequate but not comprehensive.

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% for both parameters, so the description adds little beyond the schema. It explicitly mentions 'for ASINs' but does not elaborate on the 'domain' parameter, which the schema already describes as having a default. The description's value is in explaining return content, not parameter meaning.

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 uses a specific verb ('Get') and identifies a distinct resource ('buy box ownership info') with immediate context (current seller, FBA status, offers). This clearly differentiates it from sibling tools focused on price history, product details, or variations.

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 usage context (checking buy box ownership for ASINs) but provides no explicit guidance on when to choose this tool over siblings or any exclusions. It does not state conditions like requiring a domain or number of ASINs, leaving the agent to infer from the schema.

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