Get ABC News section headlines by passing a section slug (us, world, politics, business, technology, entertainment, health, sports). Returns clean JSON for any application.
Get ABC News section headlines. Returns fresh headlines from one ABC News section's public hub page.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | ABC News 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 carries the full behavioral burden. It adds context about returning 'fresh' headlines from a public hub page, implying a read-only operation, but does not detail limits, errors, or output format.
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 core action is front-loaded, and additional context is minimal 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 one-parameter read tool, the description covers the purpose, source, and result. It lacks explicit return-structure details, but for headlines this is probably sufficient.
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?
Schema coverage is 100% and the only parameter (section) is fully enumerated with descriptions. The description adds no new meaning beyond the schema, so baseline 3 applies.
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: getting ABC News section headlines. It clearly communicates the tool's function, though it does not explicitly differentiate from siblings like abcnews_news or other headline tools.
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?
There is no guidance on when to choose this tool over alternatives such as abcnews_news, abcnews_sections, or other publishers' headline tools. No exclusions or conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.