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

Annotations only say readOnly and openWorld; the description adds substantive behavior the agent could not otherwise know: continuation pages return feed only, all identity fields are null from page two onward, ASINs are limited to the first screenful while itemCount is the true total, and each call costs 1 credit. These are exactly the non-obvious traits that would otherwise cause misinterpretation of results.

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?

Front-loaded with the purpose in one sentence, then pagination, then the continuation-page caveat and credit cost — every sentence carries distinct information. Slightly dense run-on phrasing in the parenthetical field listing costs it the top mark, but there is no 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?

With no output schema, the description does the heavy lifting of describing the return shape (lists, videos, photos, ASINs vs itemCount) and pagination semantics. The only real gap is the undefined `cache_max_age` parameter and the absence of any error/failure behavior.

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 67%, and the description adds the response-side field name (`pagination.cursor`) plus the constraint that the same shop URL must accompany the token — information that is not inferable without an output schema. It does not explain `cache_max_age` at all, leaving one of three parameters undocumented in both places.

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?

States a specific resource (a creator's public Amazon storefront) and enumerates exactly what it returns: profile name, exposed product links, idea lists with itemCount, shoppable videos and photos. This clearly separates it from siblings like amazon_product, amazon_search and amazon_offers, which return catalog objects rather than a storefront feed.

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 first request needs no pageToken" and "Pass `pagination.cursor` back as `pageToken`, unchanged, with the same shop URL" give explicit operational guidance for the paginated flow. It never names a sibling alternative or a when-not-to-use case (e.g. versus amazon_product for a single ASIN), 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.