Get current trending/headline news.
Args:
scope: "korea" (Korean headlines) or "tech" (global tech trends)
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | korea |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'current trending/headline news' but does not describe recency, source scope, potential duplicates with sibling tools, pagination, or return shape. For an unannotated read tool, this is a minimal disclosure.
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 short, front-loaded with the core purpose, and every line adds meaningful information. The scope definitions are compact and directly useful, 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?
The tool is simple with one parameter and has an output schema, so basic return information is covered elsewhere. However, the existence of strongly overlapping siblings like korean_news and tech_news creates a context gap: the description does not clarify which tool is preferred in which scenario.
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%, and the schema only declares a default value for 'scope' with no description or enum. The description fully compensates by defining the allowed values 'korea' and 'tech' and their meanings, making the parameter actionable for an agent.
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 ('Get') and resource ('current trending/headline news'), and it defines two scopes: 'korea' for Korean headlines and 'tech' for global tech trends. It does not explicitly differentiate from sibling tools like korean_news and tech_news, but the purpose itself is understandable.
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 gives the scope options and what each returns, but it does not explain when to use this tool instead of siblings such as tech_news, korean_news, or news_search. There is no explicit when-not or alternative routing, leaving the agent to guess based on tool names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct: daily_briefing is a curated combined digest, korean_news is category-based, tech_news is topic-specific, news_search is keyword search, read_article extracts content, and trending shows top headlines. Minor overlap exists between daily_briefing and the other fetch tools, but each serves a clear purpose.
All tool names use snake_case, but the pattern isn't uniform—some are adjective_noun (korean_news, tech_news, daily_briefing), some noun_verb (news_search), and one gerund (trending). Despite the mixed structure, the naming is readable and predictable enough.
With 6 tools, the server is well-scoped for a news hub. Each tool covers a distinct content need without redundancy, and the count feels neither thin nor bloated.
The surface covers core news workflows: browse by category or topic, search, read full articles, and get trending headlines. Missing features like custom briefings or language-specific search for korean_news are minor and don't break the primary use case.