Fetches headlines from a specified Breitbart section. Returns structured JSON for topics like politics, economy, tech, and world-news.
Get Breitbart section headlines. Returns fresh headlines from one public Breitbart section hub page.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Breitbart section 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 fully carries the behavioral burden. It discloses that headlines are 'fresh' and from a 'public' hub page, implying a read-only operation with no authentication. However, it lacks details on rate limits, pagination, or response structure, so it provides only partial transparency.
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 concise sentences with zero extraneous content. The primary purpose is stated immediately, and the additional context about freshness and source is brief and relevant.
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 tool with one parameter and no output schema, the description covers the essential purpose and basic behavior. It mentions freshness and public access, which is sufficient for an agent to invoke it correctly. Minor gaps like response format or rate limits are not critical for this simple operation.
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 already fully documents the 'section' parameter with an enum of valid slugs and a description. The tool description adds no additional semantic information, so the baseline score of 3 is appropriate given 100% schema coverage.
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 tool 'Get Breitbart section headlines' with a specific verb and resource, and adds that it returns fresh headlines from a section hub page. It differentiates from other Breitbart tools by focusing on 'section headlines', but does not explicitly name what it is not, so a 4 is appropriate.
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?
No guidance is provided on when to use this tool versus alternatives like breitbart_news or breitbart_sections, nor any mention of when not to use it. The description only describes what it does, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.