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

Annotations already cover read-only, idempotent, and open-world behavior, but the description adds material business behavior: the first page is a priced search and later pages with cursor > 0 are free. It also discloses the response shape {items, next_cursor, has_more, trending, type}, which is valuable because there is no output schema.

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 compact and front-loaded, starting with the read operation and resource before moving into type behavior and pagination/pricing. Every sentence adds useful calling information with no filler.

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 four-parameter list tool with no output schema, the description provides enough context to choose a type, understand keyword requirements, paginate, and interpret the response shape. The main omission is the count parameter, which is relevant but not critical to a correct call.

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 0%, so the description must carry parameter meaning. It explains the type modes and keyword requirements well, and implies cursor pagination behavior, but it never explains the count parameter or its default of 20, leaving a clear gap.

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 clear verb and resource: listing TikTok trends through the TikTok Trends gateway, with four supported trend types. The TikTok platform focus helps distinguish it from siblings like list_twitter_trends or search_ig_trends, though it does not explicitly name alternatives such as search_tt_videos or get_tt_trend_analysis.

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?

It gives useful type-specific guidance: HASHTAGS requires a keyword, MUSIC supports trending sounds or keyword search, and CATEGORIES/EFFECTS return TikTok trending lists. However, it does not say when to use this tool instead of related siblings like search_tt_videos, analyze_tt_trend_media, or get_tt_trend_analysis.

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