Fetch headlines from a chosen NBC News RSS section, such as politics, business, or health, to monitor current coverage.
Get NBC News section headlines. Returns fresh headlines from one public NBC News RSS section. Use nbc-sections for the current value space.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | NBC News RSS section slug: news, world, us-news, politics, business, science, or health |
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 of behavioral disclosure. It mentions 'Returns fresh headlines' but does not describe the output format, pagination, error handling, or any read-only/auth requirements. For a simple fetch tool, this is a notable gap.
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 two sentences with zero fluff. The primary purpose is front-loaded, and the pointer to nbc-sections is placed logically after the main action.
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 single-parameter tool with no output schema, the description provides the core purpose and a hint about valid values. However, it does not describe the return structure (e.g., list of headline objects) or behavior on invalid sections, which would be helpful for an agent.
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 fully describes the parameter with an enum and description, giving 100% coverage. The description adds valuable meaning by noting 'Use nbc-sections for the current value space', implying the enum may not be exhaustive and the values could change, which is beyond the static schema.
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 verb 'Get' and the resource 'NBC News section headlines', and specifies that it returns fresh headlines from an RSS section. It does not explicitly name sibling tools, but the purpose is distinct enough from nbc_article or nbc_news.
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?
It provides a pointer to use nbc-sections for the current value space, which is useful context for when to consult a sibling. However, it does not explicitly state when to prefer this tool over other headline tools like nyt_headlines or nbc_news, and lacks exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.