Fetch Yahoo Health homepage stories with titles, URLs, categories, and thumbnail images for building health news feeds or monitoring editorial content.
Yahoo Health homepage story stream. Returns Yahoo Health's homepage editorial story feed: title, destination URL, category, and thumbnail image for each story. Sourced from Yahoo Health's own server-rendered homepage.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden. It explains the source (server-rendered homepage) and the output fields, implying a read-only operation. However, it doesn't mention freshness, pagination, number of stories, or any rate limiting.
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?
Three sentences, all informative: the first identifies the resource, the second lists output fields, the third gives a sourcing detail. No filler or unnecessary 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?
For a zero-parameter homepage feed, the description covers the essentials: what it is, what fields are returned, and the source. It doesn't specify whether the feed is current or archived, how many stories are returned, or whether the response is paginated, but these are minor gaps for this simple tool.
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?
With 0 parameters, there is no schema detail to supplement. The description is appropriately explicit about what is returned, so an agent knows what to expect without needing 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 clearly states it returns Yahoo Health's homepage editorial story feed with specific fields (title, destination URL, category, thumbnail). It distinguishes itself from yahoo_health_article and yahoo_health_category by being a homepage feed, though it doesn't name them explicitly.
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 implies this is for fetching the Yahoo Health homepage feed without parameters, which distinguishes it from article/category tools. However, it doesn't explicitly state when to choose this over yahoo_health_article or yahoo_health_category, nor does it mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.