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

Annotations supply the safety profile (destructiveHint=false, openWorldHint=true), so the bar is lower, and the description adds real value by explaining that includeShortShareUrl enriches each comment with a short link or null while the existing shareUrl is retained. It does not address pagination behavior or the odd readOnlyHint=false on what reads as a listing operation.

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, no filler, and the core purpose is front-loaded before the optional enrichment detail. The second sentence is dense but each clause carries information about the parameter's output effect.

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?

Without an output schema, the description carries more of the burden of explaining what comes back; it only hints at return shape via the shareUrl/shortShareUrl detail and says nothing about the comment record structure beyond that. Annotations cover safety, so the remaining gap is modest but real.

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 100%, so the baseline is 3, but the description goes beyond the schema by explaining the effect of includeShortShareUrl on the returned per-comment data (short link or null, existing shareUrl retained) and framing it as an additive enrichment rather than a replacement. That is genuine semantic value on top of the schema text.

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 ('List comments on a TikTok video or photo post') and pins the platform, which is the main axis separating it from facebook_comments, instagram_comments, and youtube_comments. It stops short of naming or contrasting any sibling directly, so it is clear but not fully 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?

There is no statement of when to use this tool versus the sibling comment endpoints, nor any prerequisite or exclusion. The only conditional language ('Set includeShortShareUrl to...') is guidance on a parameter, not on tool selection.

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