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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value on top: the null-price behavior for logged-out visitors and the 1-credit cost. It stops short of describing error behavior for invalid ids/URLs, but the data-quality and quota disclosures are the important extras here.

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?

Dense and front-loaded: the resource is named first, then field inventory, then caveats, then cost. The opening 'Product details.' is near-tautological but is immediately superseded by specifics, and no sentence is wasted.

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 field enumeration does the necessary work of telling the agent what comes back, and the price caveat and credit cost round it out. Only `cache_max_age` is left entirely unexplained.

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 coverage is 67% with documented `url` and `region`; the description adds only the 'default US' detail beyond the schema's per-market note. `cache_max_age` is undocumented in both schema and description, leaving one parameter opaque.

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 resource ('A single TikTok Shop product') and enumerates the fields returned, so the agent knows exactly what it retrieves. The word 'single' implicitly distinguishes it from list/search siblings such as tiktok_shopProducts and tiktok_shopSearch without opening a schema.

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?

Gives concrete usage context for `region` (per-market catalogues, default US) and flags the logged-out data caveat that affects expectations. It does not explicitly route the agent to alternatives like tiktok_productReviews or tiktok_shopSearch, so there is context but no exclusion guidance.

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