Retrieve latest news stories from BBC News covering global, regional, and domestic stories. Returns headline, synopsis, article URL, publish date, and section (world/uk/business/tech). Use for UK perspective on international news or UK-focused stories. Includes categories for targeted browsing.
| Name | Required | Description | Default |
|---|---|---|---|
| max_results | No | Number of articles to retrieve (default 10, higher values may include older stories) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by listing exact return fields (headline, synopsis, article URL, publish date, section) and enumerating sections (world/uk/business/tech). It does not mention rate limits or pagination, but the read-only nature is covered by annotations, and the added output details are useful.
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 three concise sentences with no wasted words. It front-loads the primary purpose, then adds usage guidance, then lists output specifics, all in a logical structure. Every sentence contributes unique information.
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 simple read-only news retrieval tool with one optional parameter and no output schema, the description covers purpose, usage, and return fields sufficiently. It lacks explicit ordering/pagination details, but the schema covers max_results behavior, and the overall context is complete enough for an agent to invoke correctly.
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?
Schema coverage is 100% with the single parameter max_results having a clear description. The tool description does not reference the parameter or add additional meaning beyond the schema, so the baseline of 3 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?
The description clearly states it retrieves latest BBC News stories, specifying the resource (BBC News) and the action (retrieve). It distinguishes from sibling tools by focusing on BBC and listing the return fields (headline, synopsis, URL, publish date, section), making the tool's scope obvious.
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 explicitly says 'Use for UK perspective on international news or UK-focused stories', providing clear contextual guidance for when this tool is appropriate. This implicitly contrasts with siblings like AP/NPR for other news perspectives, fulfilling the when-to-use requirement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct news source or search functionality. The four get_* tools are differentiated by provider, and search_google_news complements them with cross-source search, eliminating ambiguity.
All tool names follow a clear verb_source pattern: get_ or search_ followed by the source identifier. This consistent convention makes the tool's function predictable from its name alone.
With five tools covering four major news providers plus a global search, the count is well-scoped for a news fetching server. Neither too sparse nor overwhelming.
The surface covers both source-specific top stories and keyword-based cross-source search, meeting the core needs of news retrieval. No critical gaps are apparent for the stated purpose.