Fetch top stories from The Sun's public RSS feed to stay updated with current headlines. Returns clean JSON data for integration.
Get The Sun top stories. Returns fresh The Sun stories from the public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It adds useful context by stating the source (public RSS feed) and that stories are 'fresh', but it does not disclose any limits, pagination, or response shape. For a simple zero-parameter read operation, this is adequate 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?
Two sentences with no filler. The primary action and resource are front-loaded, and the additional source detail is relevant. Every sentence earns its place.
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 fetch, the description is fairly complete, but it leaves a notable gap: it does not differentiate sun_news from the sibling sun_headlines, and it does not describe the return format (e.g., list of story objects). Given the number of sibling news tools, this is a moderate 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?
There are zero parameters, so the schema is trivially complete. The baseline of 4 applies because there is nothing for the description to explain about parameters; it still makes clear what the tool returns.
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 The Sun top stories') and identifies the source (public RSS feed). However, it does not distinguish this from sibling tools like sun_headlines, which likely serves a very similar purpose, so the differentiation is missing.
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?
There is no guidance on when to use this tool versus alternatives such as sun_headlines or sun_article. The description states only what the tool does, leaving the agent to infer selection criteria without any exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.