Fetch current BBC News headlines by section. Specify a section like 'world' to receive fresh headlines from the BBC RSS feed as clean JSON.
Get BBC News section headlines. Returns fresh headlines from a public BBC News RSS section. section defaults to world.
| Name | Required | Description | Default |
|---|---|---|---|
| section | No | BBC News RSS section, defaults to world |
Changes observed during successful MCP inspections.
v1.16.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present (e.g., readOnly, write, causes side effects). The description doesn't mention whether this tool makes network requests, has side effects, or whether it's customized per user, leaving behavioral expectations unclear.
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 concise sentence, 'Return current headlines from BBC News.' It is clear and free of unnecessary jargon, making it easy to parse.
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 description provides no context about the tool's data source details, update frequency, or limitations. It also doesn't indicate what output format the headlines will be in, which could matter for caller expectations.
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?
No parameters are documented. While the tool may accept none, the description lacks any statement about parameters, defaults, or examples. This is insufficient for a caller to know if optional customization (e.g., category, language) is possible.
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 returns current headlines from BBC News, leaving no ambiguity about its purpose. It is a simple, unambiguous statement.
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?
No guidance is provided on when to use this tool, expected input/output formats, or how it integrates with other tools. The description only states what it does, not how to use it effectively or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.