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

With no annotations, the description carries the behavioral burden and does disclose read-only behavior ('List' and 'Reads via Meta's loopback') plus the default scoping. It also adds context about the shared Meta-owned products table, but does not mention auth, rate limits, or error/return 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?

The description is dense but well-organized: a clear purpose sentence, a scoping/identity note, and a structured REQUIRED/Optional/EXAMPLE block. The Meta-table parity explanation is slightly technical but relevant to understanding the mirror behavior.

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 one-parameter read-only list tool, the description covers purpose, default scope, optional parameter usage, and provides an example call. Since there is no output schema, it could have described the returned product card fields more explicitly, but the core invocation context is complete.

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 0%, so the description fully compensates by explaining channel_pid's type, default behavior, valid alternatives, and the practical relevance for TikTok agents. This is substantially more useful than the bare schema property with a null default.

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 opens with a specific action and resource: 'List TikTok-owned product cards for the current user.' It further clarifies the default channel scope and notes it is a mirror of Meta's products_list, which helps distinguish it from sibling tools like products_get_actions and products_get_top_campaigns.

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 states that no arguments are required and explains exactly how to use the optional channel_pid parameter, including the 'all' union option and the recommendation that TikTok agents typically only care about tiktokglobal_int. It does not explicitly compare against alternatives, but provides sufficient context for the single optional parameter.

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