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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context with the cost disclosure ('Flat 5 points per successful run'), which is material for tool selection and implies failures are not charged. It does not, however, describe pagination or error behavior.

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 with zero waste: the identity and return payload are front-loaded, and the cost note follows. Every clause earns its place.

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, the description carries the return-value burden and does so thoroughly (price, ratings breakdown, images, specifications, features, variants, dimensions, return policy). Combined with annotations covering safety and idempotency, an agent has everything needed to call this correctly.

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 the single 'product' parameter is already documented with a type and example ('TCIN or product URL. e.g. 86216189'). The description's 'by TCIN or URL' merely restates the schema, so 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?

States a specific verb and resource ('Get one Target product') and names both lookup keys (TCIN or URL), then enumerates exactly what is returned. An agent can immediately tell this is the single-item detail endpoint, not a search. It stops short of naming the sibling it is distinct from (run_target_products_search), so it is clear but not fully sibling-differentiated.

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 'by TCIN or URL' phrasing implies the required input, which hints at when the tool applies, but there is no explicit when-to-use or when-not-to-use guidance, nor a pointer to the search tool for discovery cases. Usage is implied rather than stated.

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