target_product

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

With no annotations provided, the description carries the full burden. It discloses the type of output ('normalized product details') and enumerates key data categories (content, images, price, rating, category, availability flags). It does not mention potential side effects or error conditions, but as a read-only 'get' operation, the lack of side effects is apparent. The ambiguity around 'selected store' when store_id is optionally provided is a minor gap.

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 description is a single, front-loaded sentence that immediately identifies the tool's purpose ('Get a Target product') and then supplies the key output highlights. No redundant information or filler. Every word contributes to understanding the tool.

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?

For a simple lookup tool with two parameters and no output schema, the description provides sufficient context about what will be returned. It lists the major data categories, which covers the typical use case. Missing details like default store behavior or error handling are minor given the simplicity of the tool.

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?

The input schema describes both parameters thoroughly (tcin as numeric Target item id, store_id as Target store id for pricing/availability). The description adds marginal context by mentioning 'selected store' and 'availability flags,' but this largely mirrors the schema. Since schema coverage is 100%, the baseline of 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?

The description states a specific action: 'Get a Target product' and specifies that it returns 'normalized product details for one Target item.' This clearly distinguishes it from sibling tools like target_search, which searches for products, and target_reviews, which retrieves reviews. The verb+resource structure 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 clearly implies this tool is for fetching a single product's details using an identifier, contrasting with search tools. However, it does not explicitly mention when to use this versus target_search or other product tools, nor does it name alternatives or exclusions. The context is clear but lacks explicit alternative guidance.

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