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

Annotations already cover safety (readOnlyHint=true) and open-world reach (openWorldHint=true), so the bar is lower. The description adds genuinely useful behavior beyond that: the result ordering (rank order), the fields returned (price and rating), and a concrete cost of 10 credits. It omits pagination behavior, but the added value is real.

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?

One tightly packed sentence covers the resource, the two list types, ordering, returned fields, and cost, with no filler. Front-loaded with the resource so the agent can triage it instantly.

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 correctly takes on the burden of describing returns (rank order, price, rating), and it adds cost transparency. The remaining gap is the undocumented 'page' parameter, which an agent would have to guess at from the schema alone.

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 only 33% — only 'category' carries a description, while 'list' and 'page' are undocumented in the schema. The description partially compensates: 'Best Sellers or New Releases' maps to the 'list' enum and 'department' maps to 'category', but 'page' semantics (paging through ranked results, max 100) are not addressed anywhere.

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 and resource: retrieves Amazon Best Sellers or New Releases for a department, in rank order, with price and rating. An agent immediately knows what data comes back. It does not, however, distinguish itself from siblings like amazonProduct, amazonProducts, or amazonSearch, which also return Amazon data.

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 gives no when-to-use guidance and never names an alternative, so an agent must infer that rankings (as opposed to keyword search or single-product lookup) is the selection criterion. The only contextual signal offered is cost ('10 credits'), which is pricing, not usage guidance.

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