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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so safety is covered. The description adds a genuinely useful behavioral fact beyond that: '1 point per returned record,' a cost/credit disclosure that helps an agent reason about volume and the max_items cap.

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 compact sentences with the resource and its categories front-loaded and no padding. The credit note is short and earns its place, though the category enumeration slightly overlaps the enum.

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 annotations covering the safety profile and a fully described schema, the description supplies what's needed to invoke correctly for a read-only list tool. Return format is undocumented but no output schema exists and the shape is predictable as a list of related records.

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 description coverage is 100%, so the schema already documents all four parameters including the enum. The description restates the recommendation types but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 the resource precisely (related products shown on a Target product page) and enumerates the seven recommendation categories, which lets an agent recognize the tool's scope. It does not explicitly differentiate from nearby siblings such as run_target_products_reviews or run_target_products_questions, keeping it below a 5.

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 phrase 'on a product page' implies context of use, and listing the types hints at selection, but there is no explicit when-to-use, when-not, or named alternative (e.g., use run_target_products for the product itself). Usage must be inferred.

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