amazon_seller: GET /

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

No annotations are provided, so the description carries the full burden. It explains what data is fetched (read-only by nature) but does not explicitly state that it is a read-only operation or mention any authentication requirements. The title 'GET /' hints at read-only, but the description could be more transparent.

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 front-loaded with a clear summary sentence, followed by a list of returned data and use cases. The list could be more structured (e.g., bullet points), but it remains reasonably concise and informative.

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 tool's simplicity (3 params, no output schema), the description covers the essential aspects: input parameters, returned data, and use cases. It does not address error handling or rate limits, but for a straightforward GET endpoint, it is nearly complete.

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?

With 100% schema description coverage, the schema already explains all parameters well. The description adds no additional meaning beyond what is in the schema (e.g., default values or dependencies). 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 'Get Amazon Seller Details' and lists exactly what data is returned (business name, logo, feedback ratings, etc.). It distinguishes itself from sibling 'hasdata_amazon_seller_products_getSellerProducts' by focusing on the seller's profile 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 provides explicit use cases such as seller due-diligence, brand-protection, MAP-violation investigations, and building leaderboards. However, it does not explicitly state when not to use this tool or compare it directly to alternatives.

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