amazon_seller: GET /

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

With no annotations, the description must convey behavioral traits. It explicitly states the tool 'Fetches the public storefront profile', confirming it is a read-only operation. It does not mention rate limits or authentication, but the read-only nature is clear.

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 sentences long and efficiently conveys purpose and return data. The first sentence serves as a clear verb+resource statement, and the second provides details and use cases. It is slightly dense but well-structured.

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 compensates by listing the key data fields returned (business name, ratings, address, etc.). It also covers use cases sufficiently. No missing critical information for a seller details retrieval tool.

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?

The input schema has 100% coverage with descriptions for all three parameters. The description does not add meaning beyond the schema; it only restates the parameter roles implied by schema's descriptions and enums. Baseline 3 is appropriate.

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 fetches the public storefront profile for an Amazon seller by sellerId on a specified domain and language. It lists the specific data returned (business name, feedback ratings, etc.) and distinguishes this tool from the sibling 'hasdata_amazon_seller_products_getSellerProducts' by focusing on seller profile details rather than their 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 lists several use cases (due-diligence, brand protection, etc.) but does not explicitly compare this tool to alternatives like 'getSellerProducts'. Usage context is implied but could be clearer on when not to use it.

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