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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-scope profile is covered. The description contributes one genuinely useful non-annotation fact: the call costs 1 credit, which matters for budgeting. It says nothing about return shape, pagination, or how 'trending' is computed, which keeps it at a middling score.

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 compact fragments, scoping detail front-loaded, and no filler whatsoever. The cost note is set apart in parentheses, which reads cleanly. It is perhaps over-terse rather than bloated, so no penalty on this dimension.

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?

There is no output schema and no annotation beyond read-only/open-world, so the description is the only place an agent could learn what the feed actually returns (videos, hashtags, sounds?), whether region defaults to something when omitted, or whether results are paginated. It also fails to resolve its overlap with tiktok_trending_feed. For a tool with zero output documentation, this is too thin.

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% and the single 'region' parameter is fully described as a two-letter country code in the schema itself, so the schema carries the load. The description reinforces that results are region-scoped, which is the only semantic the parameter has. With one well-documented optional param, this is close to the ceiling.

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 resource (trending feed) and a scope (a region), so the general purpose is graspable. But the sibling list contains tiktok_trending_feed, which is nearly identical in name and meaning, and the description makes no attempt to say how this differs. The agent is left to guess between two apparent duplicates.

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 when-to-use guidance, no exclusions, and no pointer to alternatives such as tiktok_trending_feed, tiktok_search_hashtag, or twitter_trends for cross-platform trend work. The only implied usage is 'call it for trending content', which the agent could infer from the name alone.

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