Retrieves the current list of CBS News RSS sections, providing verified section names for use in news headline queries.
Get CBS News sections. Returns the live-verified public CBS News RSS section inventory used by cbsnews-headlines.
| 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?
No annotations are provided, so the description carries the full burden. It usefully discloses that the data is public, live-verified, and RSS-based, and that the tool returns an inventory rather than a confirmation or status. It stops short of describing failure behavior or response size, but for a zero-parameter getter this is solid context.
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 front-loaded sentences with no wasted words: the first gives the action in a compact phrase, and the second adds the meaningful detail about what is returned and its relationship to cbsnews-headlines.
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 tool with no output schema, the description explains the return concept ('section inventory') and its consumer ('cbsnews-headlines'). It does not specify the exact structure or fields of the inventory, but that is a minor gap for this simple list-like endpoint.
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 input schema has zero parameters and schema description coverage is 100%, so there are no parameter semantics for the description to clarify. Per the zero-parameter baseline, a score of 4 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?
States a specific verb ('Get'), a specific resource ('CBS News sections'), and identifies the exact output: the live-verified public CBS News RSS section inventory used by cbsnews-headlines. This clearly sets it apart from sibling tools like cbsnews_headlines or cbsnews_news, even without naming them.
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?
Implies usage by noting the inventory is 'used by cbsnews-headlines', so an agent can infer this tool should be called to obtain section identifiers before fetching headlines. However, it never explicitly states when to use this tool versus alternatives or gives any exclusions, so the guidance remains indirect.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.