search_trending_videos

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

No annotations provided, so description carries full burden. States it returns video titles, views, likes, indicating a read-only operation. Notes 'FREE', suggesting no cost. Lacks details on auth, rate limits, or pagination, but for a simple search tool, disclosure is adequate.

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 concise sentences with front-loaded purpose. The 'FREE:' prefix is minor and not essential, but the description is otherwise efficient and easy to parse.

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?

Tool is simple with one parameter and no output schema. Description specifies what it does and returns basic fields, but lacks details on result count, sorting, pagination, or limits. Sufficient for a basic search but could be more complete.

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 has 100% coverage with a clear description for the only parameter (keyword). The tool description adds no new parameter information beyond what the schema provides, so baseline 3 applies.

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?

Clearly states 'Search for trending TikTok videos by keyword/hashtag', specifying the action and resource. Distinguishes from sibling tools (analyze_hashtag, draft_video_script, etc.) by focusing on video search rather than analysis or creation.

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 guidance. The description implies usage for finding trending videos by keyword, but does not contrast with alternatives or mention prerequisites. The context of sibling tools somewhat clarifies, but the description itself lacks direct instruction.

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