Retrieve fresh headlines from a specific ProPublica topic feed by providing its slug. Returns JSON headlines for the selected section.
Get ProPublica topic headlines. Returns fresh headlines from one public ProPublica topic feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | ProPublica topic slug |
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 carries the burden of behavioral disclosure. It does state that the tool 'returns fresh headlines' and that the feed is 'public,' suggesting a read-only, accessible operation. It does not describe return shape, sorting, pagination, or rate limits, which an agent might need for a feed 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?
Two short sentences communicate scope and return behavior with minimal waste. The core action is front-loaded, and the second sentence adds value by specifying freshness and the public-feed nature rather than repeating the schema.
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 one-parameter read tool with a fully documented enum, the description is largely sufficient for an agent to select and invoke it correctly. The lack of an output schema and any detail about headline count or included fields leaves minor ambiguity, but not a serious gap.
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 input schema provides 100% coverage: the required 'section' parameter is described as a 'ProPublica topic slug' with an exhaustive enum. The description merely reinforces that a topic feed is involved and adds no additional format or selection semantics, so the schema already does the heavy lifting.
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 ProPublica topic headlines,' and adds that it returns 'fresh headlines from one public ProPublica topic feed.' This makes the tool's function clear, though it does not explicitly distinguish it from sibling tools like propublica_news or propublica_sections.
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 intended use case is implied: fetch current headlines for a specific ProPublica topic. However, the description gives no when-not guidance or named alternatives, so an agent must infer when to choose this tool over related ProPublica or other news-headline tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.