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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds two real facts: an authentication prerequisite (configured TikTok signer) and a billing cost (1 credit). It stops short of noting pagination or result-shape behaviour, but that is close to the schema's job.

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?

Four short sentences, front-loaded with the concept, then the differentiating nuance, then prerequisites and cost. The opening restates the title almost verbatim, which is the only wasted line.

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 still conveys what the entity is, how it differs from adjacent product tools, that auth setup is required, and that it costs credits — everything needed to decide and call correctly. Remaining details (pagination, market scoping) live in a well-covered schema.

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 80%, so nearly every parameter is documented in the schema itself (count limits, cursor provenance, handle format, region semantics). The description adds nothing parameter-specific and leaves cache_max_age unexplained in both places, so 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 resource (products pinned to a creator's profile showcase) with a scope qualifier distinguishing it from products the creator merely sells. The distinction gestures at siblings like tiktok_product and tiktok_shopProducts, but never names them.

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 line 'This is what they are actually promoting, as opposed to what they sell' implies when to pick this over a shop/catalog tool, and 'Requires a configured TikTok signer' is a useful prerequisite. There is no explicit 'use X instead when Y' routing, so the guidance remains implicit.

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