Fetch SBS News headlines for a specific section, including top, world, politics, sport, and more, by providing the section slug.
Get SBS News section headlines. Returns current SBS News headlines for a supported navigation or featured topic section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Section slug from sbsnews-sections |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only retrieval and says headlines are 'current', but does not disclose how many items are returned, whether results are ordered or paginated, or how frequently they refresh. For a news-retrieval tool with zero annotation coverage, this is thin.
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 short sentences, purpose front-loaded in the first, no wasted preamble. The second sentence largely restates the first with minor added scope, so it is efficient but not maximally tight.
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 single-parameter read tool with no output schema and no annotations, the description covers what is fetched and from where, which is close to sufficient. It leaves the return shape, item count, and ordering unspecified, so it is adequate but with clear gaps.
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% and the single enum parameter is fully documented with its allowed values plus a pointer to sbsnews-sections. The description's 'supported navigation or featured topic section' mirrors the schema rather than adding format or validation detail, so the 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?
States a specific verb (Get) and resource (SBS News section headlines), and clarifies the scope as 'current' headlines for a navigation or featured topic section. It is distinguishable from the sibling sbsnews_article/sbsnews_news tools by the 'headlines' framing, though it never explicitly contrasts with them.
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 when-to-use guidance, no exclusions, and no mention of alternatives such as sbsnews_news, sbsnews_sections, or sbsnews_article. The agent must infer that this tool is for fetching headline listings rather than full articles.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.