Search news by keyword.
Args:
query: Search keyword (e.g. "Samsung AI", "Claude Code", "MCP server")
language: "ko" (Korean) or "en" (English)
count: Number of articles (default 10, max 20)
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| query | Yes | ||
| language | No | ko |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It does disclose useful constraints like count max 20 and the allowed language values, and the operation is clearly a read-only news search, but it does not describe result behavior such as relevance ordering, freshness, or article metadata beyond what the output schema provides.
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. The one-line purpose is immediately followed by a tight, well-organized Args block with no filler or redundant explanation.
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 simple three-parameter search tool with an output schema, the description covers everything needed to invoke it correctly, including defaults, maximums, and allowed values. The only missing context is clearer guidance on selecting this tool over the sibling news tools, which is a minor completeness gap.
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?
The schema only supplies names, types, and defaults, so the description's Args block adds essential meaning: query examples, explicit language values ('ko' or 'en'), and count default/max. This fully compensates for the 0% schema description coverage.
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 specific action and resource: 'Search news by keyword.' It is immediately understandable and distinct from read_article or daily_briefing, but it does not explicitly distinguish itself from sibling news-list tools like korean_news, tech_news, or trending, so it stops short of full sibling differentiation.
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 phrase 'by keyword' implies this is the tool to use for query-driven news lookups rather than curated lists, but there is no explicit when-to-use/when-not-to-use guidance and no mention of alternative sibling tools. The usage context is present only by implication.
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.