Target Product

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds useful context beyond that: the call routes through the Decodo Web Scraping API, the payload is parsed to JSON, and it returns price/availability/description. It doesn't mention failure modes, rate limits, or blocking risk, which a scraper tool could reasonably disclose.

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?

Three tight sentences with the action and the return shape front-loaded, followed by the selection hint. The docs URL is a minor but justified addition; nothing is redundant with the title.

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?

No output schema exists, so the description usefully names what comes back (price, availability, description) as parsed JSON. For a single-required-param read tool with full annotation coverage, that is close to sufficient; only error/empty-result behavior is unaddressed.

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% and every parameter including product_id, jsRender, deviceType and deliveryZip is documented in the schema itself. The description adds no syntax or constraint detail beyond that, so the baseline 3 applies.

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 ('Fetch a Target product page by product ID'), names the underlying API target, and says the result is JSON-parsed details. This clearly separates it from target_search, which would be the discovery path rather than a known-ID lookup.

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?

'Use it when you know a Target product ID and need its price, availability or description' gives a concrete trigger condition. It stops short of naming target_search as the explicit fallback when you don't have an ID, which keeps it out of 5 territory.

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