Retrieve CBS Sports top stories from the public headlines RSS feed, returning current sports news in structured JSON.
Get CBS Sports top stories. Returns fresh CBS Sports top stories from its public headlines 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 provided, the description carries the full burden. It discloses the source (public RSS feed) and that results are 'fresh,' which is useful, but it does not describe output structure, potential limits, or how the returned stories are represented.
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 brief sentences with no filler. The primary action and resource are front-loaded, and 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?
The tool is simple with no parameters, but there is no output schema, so the description should clarify what the returned 'stories' contain. It says 'top stories' from an RSS feed but leaves the response shape unspecified and does not address the relationship to sibling tools.
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 tool has zero parameters, so there are no parameter semantics for the description to add. The baseline of 4 for zero-parameter tools applies.
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 clear verb ('Get') and resource ('CBS Sports top stories'), and adds the source ('public headlines RSS feed'). It communicates the function distinctly, though it does not explicitly differentiate from the sibling cbssports_headlines.
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 when fresh top stories are needed, and the RSS feed mention gives context, but it provides no explicit when-to-use vs. alternatives or exclusions. It does not clarify when to choose cbssports_news over cbssports_headlines or cbssports_sections.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.