Fetch fresh Foreign Policy site-wide headlines from its public RSS feed; use foreignpolicy-topic to scope results by category or tag.
Get Foreign Policy site-wide headlines. Returns fresh headlines from Foreign Policy's public, site-wide RSS feed. There is no section parameter: use foreignpolicy-topic to scope to one category or tag.
| 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 provided, the description carries the full burden. It discloses that the data comes from a public RSS feed, is site-wide, and is fresh, and it clarifies the absence of a section parameter. However, it does not describe the output structure (e.g., list of items with titles and links), which would be useful but is not critical for a simple headlines tool.
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 no filler. The purpose is front-loaded, and the second sentence adds essential scoping guidance. Every sentence earns its place.
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 tool with no parameters and no output schema, this description is complete: it states the action, the source (RSS feed), freshness, scope, and the alternative for scoped queries. Nothing an agent needs to call it correctly is missing.
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 tool has zero parameters, and the description explicitly notes that there is no section parameter, which is informative. Per the baseline for zero-parameter tools (score 4), the description adds a helpful clarification that prevents misuse.
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 action (Get) and the resource (Foreign Policy site-wide headlines). It explicitly differentiates from the sibling foreignpolicy-topic by noting there is no section parameter, making the tool's scope unambiguous.
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 explicit usage guidance: use this tool for site-wide headlines, and use foreignpolicy-topic when you need to scope to a category or tag. This clearly routes the agent to the correct tool based on need.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.