Fetch USA Today section headlines for a chosen top-level section, such as news, sports, or tech.
Get USA Today section headlines. Returns the newest items from one top-level USA Today section, filtered from the same public news feed as /usatoday/news.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Top-level USA Today section |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. It adds useful behavioral context by stating the feed is public and that results are the 'newest items', but it does not disclose output shape, pagination, result count, or any limiting behavior. This is minimally viable but not rich.
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 tight sentences with the action and scope front-loaded. The second sentence earns its place by clarifying the data source and filtered relationship to /usatoday/news; there is no filler.
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?
The tool is low-complexity with one fully documented enum parameter, and the description covers source, recency, and single-section scope. It lacks an explicit response-shape statement, but 'headlines' and 'returns the newest items' are enough for an agent to call it correctly without an output schema.
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 section parameter already has an enum plus a description ('Top-level USA Today section'). The description reinforces 'top-level' and 'one section' but adds no meaning beyond the schema, so the high-coverage baseline of 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 ('Get'), a specific resource ('USA Today section headlines'), and a clear scope ('one top-level USA Today section'). It also distinguishes itself from the broader feed by saying it is 'filtered from the same public news feed as /usatoday/news'.
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 clear context: use this when you need the newest headlines from a single top-level USA Today section, and it positions itself as a filtered view of the /usatoday/news feed. It does not explicitly name an alternative for all-headlines use, so it stops short of full when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.