Fetch current headlines from any 7NEWS Australia section by providing the topic slug. Returns the 100 most recent stories for that section.
Get 7NEWS Australia section headlines. Returns fresh 7NEWS headlines from one public topic feed (the 100 most recent stories tagged with that topic).
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | 7NEWS topic slug (the site path with slashes replaced by hyphens) |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It mentions freshness ('fresh'), a cap ('100 most recent stories'), and public availability, which are useful traits. It does not cover rate limits or output structure, but for a simple read operation this is adequate.
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 a single sentence, front-loaded with the key action, and contains no filler. It efficiently conveys the tool's purpose and scope.
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?
Given the single-parameter design and no output schema, the description sufficiently covers what an agent needs: it states the resource, the feed cap, and the topic-based nature. It does not detail the return format, but 'headlines' is interpretable. Minor lack of explicit note about the enum validation is acceptable.
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% because the parameter description ('7NEWS topic slug (the site path with slashes replaced by hyphens)') explains the format. The tool description adds no extra parameter context, so the schema is the primary source. 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 clearly states a specific verb ('Get'), a specific resource ('7NEWS Australia section headlines'), and clarifies the scope (a public topic feed of the 100 most recent stories). This distinguishes it from other news headline tools and from sevennewsau_article, sevennewsau_news, etc.
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 description implies usage for 7NEWS Australia headlines but does not explicitly contrast with sibling tools like sevennewsau_news or sevennewsau_sections, nor does it state when not to use this tool. It communicates the feed scope (one topic, 100 stories) but lacks explicit alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.