amazon_seller: GET /

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

With no annotations, the description carries the behavioral burden. It clearly indicates a non-destructive read of public data ('Fetches the public storefront profile') and enumerates return content. It does not discuss rate limits, failure modes, or authentication, but 'public' and 'fetches' make the core behavior 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 body is front-loaded with the core operation, followed by useful return-content and use-case context. The heading line 'Get Amazon Seller Details' duplicates the tool name, and the use-case list is slightly long, but there is no true filler.

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?

For a read-only look-up with 3 parameters and no output schema, the description is complete: it identifies what is returned, the required identifier, the domain/language context, and the use cases that justify selecting the tool. No critical selection or invocation information is missing.

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 schema already documents sellerId, domain, and language. The description adds only that the fetch is 'by sellerId on the chosen domain/language,' which maps to the parameters but does not add new semantic detail beyond the schema.

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 states a specific operation — fetches the public storefront profile for an Amazon seller by sellerId on a domain/language — and names the resource (seller profile) and scope. It is clearly distinct from sibling tools focused on product details, reviews, search results, or seller product listings.

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?

It gives explicit use cases (seller due-diligence, vetting, counterfeit/brand-protection, MAP-violation investigations, leaderboards, seller-directory enrichment), so an agent knows the intended context. It does not explicitly say when NOT to use it or name an alternative tool, so it stops short of full routing guidance.

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