run_target_products_recommendations

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

No annotations are provided, so the description carries the full burden. It does disclose a genuine behavioral trait beyond the schema: '1 point per returned record', which is useful cost/capacity context for a paid scraper. However, it says nothing about read-only safety, pagination behavior, or auth requirements, leaving significant gaps for a no-annotation tool.

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 tight sentences with the resource front-loaded and the cost note following. The category list slightly duplicates the enum, but it is the tool's core value and reads efficiently overall.

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 and no annotations, the description should carry more weight. It conveys what the tool returns and the point cost, but omits return shape, pagination semantics (start_page) and usage context, leaving it only minimally adequate for a 4-parameter scraper.

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 mapping. The description's list of categories mirrors the enum options and adds no new meaning or syntax detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description names the specific resource and frame: 'Related products Target shows on a product page', which tells an agent exactly what data comes back. It enumerates the recommendation categories, further disambiguating it from sibling Target tools like run_target_products_reviews and run_target_products_search. It lacks an explicit action verb ('retrieve/list') but the intent 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?

There is no when-to-use guidance, no prerequisites, and no named alternative among the many sibling tools. It describes the return payload but leaves an agent to infer when recommendation data is preferable to, say, run_target_products or run_target_products_search.

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