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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely useful behavioral context beyond that: output format (CSV/JSON), the exact fields returned, coverage across all marketplaces, and a concrete cost of $4 per 1,000 reviews. It omits rate limits, auth requirements, and pagination/completeness limits, but the cost and format disclosure is real added value.

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 core sentence is well front-loaded with verb, resource, and output fields, but the content is literally duplicated (the first sentence is a truncated version of the second), which is wasted space and reads as an authoring error.

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 usefully compensates by naming the returned fields and output formats, and it adds pricing and marketplace scope. The main remaining gap is input specification, which is deferred to an external URL rather than resolved in the schema.

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?

There is a single nested 'input' object with 100% schema description coverage, but that coverage is only a pointer to an external Apify page rather than field-level documentation. The description adds no parameter meaning at all — no mention of what inputs are required or optional — so it sits at the baseline.

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?

Names a specific verb (scrape) and resource (Amazon product reviews) and enumerates the extracted fields (rating, body, author, date, verified-purchase). It does not distinguish itself from near-siblings like universal_review_insights or app_review_intelligence that also return review data, but the Amazon-specific scope is unambiguous.

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 never states when to choose this tool over the review-oriented siblings, nor any preconditions (e.g., product URL/ASIN needed, marketplace selection). Pricing and output format are given, but no routing guidance.

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