Get Korean news by category.
Args:
category: News category. Options: 속보, 정치, 경제, 사회, IT, 세계, 연예, 스포츠
count: Number of articles (default 10, max 20)
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| category | No | 속보 |
| 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 behavioral disclosure burden. It clearly signals read-only behavior via 'Get,' and the output schema covers return structure, but it does not mention potential side effects, auth requirements, or whether it returns headlines versus full articles. For a simple fetch tool this is acceptable but not rich.
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 tightly written: a one-line summary followed by compact parameter details. Every sentence adds information, and there is no redundant filler. The front-loaded summary makes the tool's purpose immediately clear.
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 two-parameter fetch tool with an output schema, this is nearly complete: category options and count bounds are covered. The main omission is explicit guidance on how this tool relates to siblings such as news_search and tech_news, which would help an agent choose correctly.
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%, and the description fully compensates by documenting both parameters. It lists all valid category options and specifies count's default and maximum, which the bare schema does not provide. This is essential, actionable parameter documentation.
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 uses a specific verb and resource: 'Get Korean news by category.' It immediately differentiates from siblings like tech_news (Korean vs. tech-focused) and news_search (category listing vs. search). It is not a tautology and gives a clear, concrete action.
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 category list and count parameters imply the tool is for fetching Korean news in a given category, but there is no explicit guidance on when to prefer this over siblings like news_search, tech_news, or read_article. Usage context is only implied, not stated.
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.