Fetch Newsweek top stories from the public feed; returns headline items from the general top-story stream. For a section-specific list, use newsweek_headlines with a supported section slug. Use newsweek_article with a returned article URL when you need one story's body.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real context beyond them: the data comes from a public feed and returns 'headline items' from a general stream, clarifying scope and grain of the result. It stops short of describing pagination or item count, so not a full 5.
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 tight sentences, front-loaded with the core action, then two routing clauses. Every sentence earns its place with no redundancy.
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?
An output schema exists, so return-shape detail is unnecessary. For a zero-parameter, read-only feed endpoint the description supplies everything an agent needs: purpose, scope, and correct sibling routing.
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 is an empty object with zero parameters, so there are no parameter semantics to document; baseline 4 applies. The description correctly implies no filtering is possible on this tool and routes filtering needs elsewhere.
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 (Fetch) and resource (Newsweek top stories) with the scope 'general top-story stream' made explicit. It distinguishes itself from sibling newsweek_headlines (section-specific) and newsweek_article (single body), so an agent can route without opening any 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?
Gives explicit when-to-use (top-story stream) and names both alternatives with the condition that selects each: section slug lists go to newsweek_headlines, single body goes to newsweek_article via a returned URL. Nothing is left to inference.
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.
