Get current top stories from Deutsche Welle. Retrieve clean JSON data containing the title, summary, URL, and publication time of DW's main headlines.
Get DW top stories. Returns the current Deutsche Welle top stories. Each item has its title, URL, summary and publication time. Takes no parameters; use dw-headlines for a single region, topic or category.
| 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, the description still discloses the important behavior: it is a no-parameter call, it returns current top stories, and each item contains title, URL, summary, and publication time. It does not mention rate limits or authentication, but for a read-only news feed this is a solid level of disclosure.
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?
Three short sentences, front-loaded with the primary purpose, then return details, then the alternative-tool guidance. No sentence is redundant.
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 has no input schema, no output schema, and no annotations, so the description carries the full burden and does so adequately: it explains the output fields, confirms the no-parameter nature, and names the appropriate sibling for narrower queries.
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?
There are zero parameters, which sets the baseline at 4. The description reinforces this by explicitly stating 'Takes no parameters,' so there is no ambiguity about invocation.
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 specific verb and resource ('Get DW top stories'), confirms it returns current Deutsche Welle top stories, and lists the item fields. It also distinguishes itself from the sibling headlines tool, so an agent can identify it without opening the schema.
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 explicitly says the tool takes no parameters and directs the agent to `dw-headlines` when a single region, topic, or category is needed. That is a clear when-to-use-this vs when-to-use-an-alternative rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.