Retrieve current headlines from any Sky News section by specifying its slug. Uses official RSS feeds or public hub pages to return fresh headlines as clean JSON.
Get Sky News section headlines. Returns fresh headlines from one Sky News section, either its official RSS feed or (for the 5 sections with no feed) its public hub page.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Sky News section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that data comes from RSS feeds or hub pages, and notes that some sections have no feed, which is useful behavioral context. It does not mention pagination or return format, but for a simple headlines fetch, the description provides adequate transparency.
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, focused sentence that front-loads the main action and adds a clarifying parenthetical. No wasted words; every clause adds value.
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 single-parameter tool without output schema, the description covers the essential: what it returns and the data source. It could mention that the response is a list of headlines, but that's implied by 'headlines.' The description is complete enough for an agent to call it 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?
The schema already lists the section parameter with an enum and description ('Sky News section slug'). The description adds slight context about which sections lack feeds but doesn't explain the parameter's format beyond what the schema provides. Schema coverage is 100%, so baseline 3 is appropriate.
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 fetches headlines from a Sky News section and mentions the data source (RSS feed or hub page). It distinguishes itself from related tools like skynews_article and skynews_sections by focusing on headlines, though it doesn't explicitly name alternatives.
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 usage for retrieving section headlines but does not explicitly state when to use this tool versus others like skynews_news or skynews_sections. It gives context about the source but no exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.