Fetch current The National stories for a specified editorial section slug, returning structured headlines or an empty list if none exist.
Get The National section headlines. Returns current The National stories for a category. Pass one of the editorial section slugs from national_sections. A valid category with no current stories returns an empty items list.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | The National editorial section slug |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses the empty-result edge case ('A valid category with no current stories returns an empty items list'), but omits other traits like auth requirements, rate limits, or response field details.
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?
Four short sentences, each earning its place: purpose, clarification, parameter source, and edge case. The purpose is front-loaded and there is no wasted wording.
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 with a rich enum schema and no output schema, the description covers purpose, parameter source, and empty-result behavior. It could still mention the shape of returned items or pagination, but nothing essential 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?
Schema description coverage is 100%, so the baseline is 3. The description adds that valid slugs come from national_sections, but this is a minor addition beyond the enum and schema description already present.
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 The National section headlines' and 'Returns current The National stories for a category.' It clearly scopes the tool to section headlines, but does not explicitly differentiate it from siblings like national_news or national_article, so it falls short of a 5.
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 gives a prerequisite by telling the agent to 'Pass one of the editorial section slugs from national_sections,' which is useful usage context. However, it does not state when to use this tool instead of alternatives such as national_news or national_article, leaving the choice to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.