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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, but the description adds genuinely new behavioral facts: a $0.002 per-call cost in USDC via x402 across Base/Solana/Arc, and that failed calls are not charged. It also discloses the field-level return shape and sorting behavior; only pagination/rate behavior is left implicit.

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?

Two sentences, front-loaded with what is fetched and keyed on, followed by a compact pricing/payment sentence. The field enumeration is dense but each item tells the agent what data it will get back, so nothing is wasteful.

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?

Given a five-parameter schema that is fully documented, an output schema, and annotations covering read-only/open-world, the description covers everything an agent needs: how to identify the product, which knobs exist, what data returns, and the cost/payment model. Nothing material is missing for correct invocation.

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 meaning beyond the schema by explaining where the TCIN comes from in a target.com URL and by spelling out the sort semantics ('most recent, most helpful, highest or lowest') and the verified-only filter. The page and limit parameters remain unelaborated beyond their schema descriptions.

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 ('Reviews of a Target product by TCIN') and immediately enumerates the payload (rating statistics plus individual reviews with named fields). No sibling tool covers Target reviews, so the retailer-plus-resource naming is enough to distinguish it.

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 explains how to obtain the required TCIN ('the number after A- in a target.com product URL') and enumerates sort and verified-only options, which guides invocation. However, it never states when to prefer this tool over an alternative or any prerequisite/exclusion conditions, so usage is implied rather than prescribed.

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