get_daily_horoscope'오늘의 운세', '오늘 운세 알려줘', '띠별 운세'처럼 그날의 운세를 물을 때 사용합니다. 운세 내용은 포함하지 않고 제목·발행일·원문 링크만 반환하며, 운세 본문은 다른 기사와 동일하게 item.url 의 한국일보 원문에서만 확인할 수 있습니다. 기본은 오늘(한국 시간)이며, date(YYYY-MM-DD)로 특정 날짜를 지정할 수 있습니다.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | 조회할 날짜(YYYY-MM-DD). 생략 시 오늘(한국 시간) 운세. |
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | 반환된 운세의 발행 일시. | |
| item | No | 운세 기사 카드(메타데이터·원문 링크만, 운세 내용 미포함). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint, openWorldHint) indicate safe, read-only operation. The description adds that only title, date, and link are returned, and the fortune text must be obtained from the original source. This provides additional transparency beyond annotations.
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 a single, efficient paragraph that front-loads the use case. Every sentence adds value: when to use, what it returns, what it doesn't, how to get full content, and parameter details. No wasted words.
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's simplicity and the presence of an output schema (documenting return values), the description covers all necessary aspects: usage context, return structure limitations, parameter explanation, and default behavior. It is fully 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?
The single optional parameter 'date' is well-described in both schema and description. The description reiterates the format (YYYY-MM-DD) and default behavior (today Korean time), adding clarity beyond the schema. Schema coverage is 100%, so baseline is 3, but description adds value.
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 returns horoscope metadata (title, date, link) for a given date, and it distinguishes itself from the sibling tool 'get_mbti_horoscope' and other news tools. The verb '사용합니다' indicates the use case for daily fortune questions.
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?
Explicitly states when to use (when asking about daily horoscope). It explains that the actual content is not returned and must be accessed via the original link, providing implicit guidance on alternatives. However, it does not explicitly list when not to use.
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.
Each tool targets a distinct purpose: horoscopes (daily vs MBTI), news listings (latest, most read, popular, recommended, timely, top headlines), sections, and search. Descriptions provide clear usage examples and explicitly differentiate similar-sounding tools like list_most_read_news (editor-curated) vs list_popular_news (view-count based).
All tool names follow a consistent verb_noun pattern in snake_case: get_ for horoscopes, list_ for various news lists and sections, and search_ for search. No mixing of camelCase or other conventions.
10 tools is appropriate for a news server. It covers the main news consumption patterns (latest, popular, recommended, by section, search) plus two specialized horoscope tools. Neither too sparse nor overwhelming.
The tool surface covers typical news site operations: browsing latest, popular (both view-based and editor-curated), by category, headlines, time-based recommendations, and search. Horoscope retrieval is an extra feature. The missing article text retrieval is intentional (metadata-only return). No obvious gaps for the intended domain.