Amazon Shop page

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds real context beyond them: it consumes paid API credits, requires confirm=true, and clarifies that these read-like POSTs do not publish to social platforms. That materially helps an agent understand cost and side-effect profile, though rate-limit behavior is not described.

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?

Purpose is front-loaded in the first sentence, followed by return shape, pagination, token handling, and cost/auth constraints. Slightly long at five sentences but each carries distinct information with 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?

No output schema exists, but the description compensates by enumerating the returned storefront profile, collections, and video fields (id, title, thumbnail, ASINs). Combined with credit/confirm disclosure for a credit-consuming call, an agent has nearly everything needed, with only edge cases like error or empty-page behavior unaddressed.

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%, so baseline is 3, but the description adds genuine meaning: pageToken is opaque, must be passed back unchanged with the same URL, and its prefix must not be used to infer response type. This clarifies semantics beyond the schema's abbreviated token description.

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 verb (scrapes) and resource (a creator's Amazon Shop page by URL) plus what it returns (storefront profile and product collections). No sibling in the list targets Amazon Shop pages, so an agent can distinguish this tool by resource alone.

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?

Provides workflow guidance on pagination (pass each token back unchanged with the same shop URL; initial request needs no token) and notes confirm=true is required. However it never states when to use this versus alternatives or any exclusion conditions, leaving usage only implied.

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