get-tencent-news-trending

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

No annotations are provided, so the description carries full burden. It mentions the content categories but doesn't disclose important behavioral aspects: whether this is a read-only operation, how frequently data updates, whether authentication is required, rate limits, pagination behavior (implied by page_size parameter but not explained), or what format/quantity of data is returned. For a tool with no annotation coverage, this leaves significant gaps.

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 appropriately concise - a single Chinese sentence that efficiently communicates the core functionality and content scope. It's front-loaded with the main purpose and doesn't contain redundant information. However, it could be slightly more structured by separating purpose from content details.

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?

Given the tool has no annotations, no output schema, and 0% schema description coverage for its parameter, the description is insufficiently complete. It covers what content is retrieved but misses critical context about how to use the parameter, what the return format looks like, behavioral constraints, and differentiation from similar tools. For a trending news fetcher with one parameter, more guidance is needed.

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 compensate for the undocumented parameter. The description mentions nothing about the 'page_size' parameter - its purpose, typical values, default behavior, or how it affects results. With one parameter completely undocumented in both schema and description, this represents a significant gap in parameter understanding.

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 clearly states the tool's purpose: '获取腾讯新闻热点榜' (get Tencent News trending list) with specific content categories including domestic/international news, social hotspots, financial information, entertainment, and sports. It distinguishes from siblings by specifying the source (Tencent News) and Chinese-language focus, though it doesn't explicitly contrast with similar tools like get-netease-news-trending or get-toutiao-trending.

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 provides no guidance on when to use this tool versus alternatives. With 19 sibling tools that appear to fetch trending content from different sources (BBC, NYTimes, Weibo, Zhihu, etc.), there's no indication of when Tencent News would be preferred over other Chinese news sources like NetEase or Toutiao, or when to use this versus general news aggregators.

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