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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely useful trait: that returned content is user-generated and should be treated as untrusted input (a prompt-injection caution). However, it omits anything about permissions, rate limits, or result ordering/pagination 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 tight sentences, front-loaded with the core purpose before the safety note. No filler or redundancy.

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?

No output schema and no annotations, so the description is the only source for return behavior, yet it says nothing about the shape of returned video records or ordering. The untrusted-input warning is useful, but for a top-N ranking tool with zero structured context the definition is only marginally adequate.

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 schema itself spells out the meaning of each sort_by enum value (diggs=digg_count, plays=view count, comments=comment count) and the limit bounds. The description merely echoes the metric names, adding nothing beyond the schema.

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 ('Get') and resource ('top TikTok videos') plus the ranking metrics, which cleanly separates it from the generic get_top_medias sibling. It does not explicitly call out that distinction, so sibling differentiation is inferential from the 'tt' prefix rather than stated.

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?

No explicit when-to-use or when-not-to-use guidance, and no named alternatives among the many get_top_* siblings (get_top_medias, get_top_tt_hashtags, etc.). Usage is only implied by the resource and metric framing.

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