Retrieve SBS News sections, including navigation and featured topic or collection pages accepted by sbsnews-headlines.
Get SBS News sections. Returns the SBS News navigation and featured public topic/collection pages accepted by sbsnews-headlines.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 must carry the behavioral burden. 'Get' plus the read-only framing makes the safe read nature clear, and the downstream hand-off to sbsnews-headlines is useful context, but there is no mention of pagination, ordering, or filtering limits.
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 zero filler, and the core action ('Get SBS News sections') is front-loaded before the return-value detail.
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, parameterless lookup with no output schema, the description adequately covers what the tool returns and how it feeds sbsnews-headlines. Only minor gaps remain around ordering or result size.
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?
The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly does not invent parameter behavior.
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+resource ('Get SBS News sections') and adds what the payload contains (navigation and featured topic/collection pages). It implicitly distinguishes itself from sbsnews_headlines by naming that tool as the consumer, though it does not explicitly contrast with sibling section 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?
The note that returned pages are 'accepted by sbsnews-headlines' implies a discover-then-pass workflow, but there is no explicit when-to-use statement or when-not to use this versus alternatives. Usage is inferable rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.