get_trending_list_tool

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

No annotations exist, so description carries the burden. It discloses the endpoint and the effect of include_history, but does not mention auth requirements, rate limits, or the required advertiser_id parameter.

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 with no extra fluff. Purpose front-loaded, parameters listed efficiently. Every sentence adds value.

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?

An output schema exists, so return values are covered. However, with 7 parameters and only 4 mentioned, and no mention of the required advertiser_id, the description feels incomplete for a tool of this complexity.

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 description must compensate. It clarifies discovery_type (HASHTAG), date_range (7DAY/30DAY), country_code (e.g. US), and include_history (per-day breakdown), but ignores 3 parameters (advertiser_id, page_size, category_id), including the required one.

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 states a specific verb and resource: 'Get trending hashtags on TikTok via /discovery/trending_list/.'. It clearly distinguishes from sibling tools (mostly ad/report tools) by focusing on trending hashtags.

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 implies usage for trending hashtags but provides no explicit guidance on when to use or avoid this tool, and no alternatives are mentioned.

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