Retrieve headlines from a specified The Straits Times section. Provide the section slug to get its headlines.
Get The Straits Times section headlines. Returns fresh headlines from one public The Straits Times section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | The Straits Times section slug |
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 is the only source of behavioral context. It adds useful details such as 'fresh' and 'public,' implying real-time data and no authentication barrier. However, it does not disclose return format, pagination, or potential limits, so the behavioral picture is only partially complete.
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 only two sentences long and immediately front-loads the action and resource. The second sentence adds distinct value ('fresh,' 'one public section') rather than repeating the first, so every word earns its place.
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 tool this is mostly adequate, but with no output schema the description never explains what a 'headlines' result contains (e.g., headline text, URLs, timestamps). It also does not clarify the relationship to sibling tools like straitstimes_news, leaving some gaps for an agent deciding which tool to call.
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 input schema fully describes the 'section' parameter with an enum of slugs and the description 'The Straits Times section slug,' so schema coverage is 100%. The description adds no additional parameter-specific guidance, and per calibration this is a baseline 3 situation.
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 action ('Get') and resource ('The Straits Times section headlines'), and further clarifies the scope with 'from one public The Straits Times section.' It does not explicitly name or differentiate from sibling tools like straitstimes_news or straitstimes_sections, which keeps it just short of a perfect score.
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 when to use the tool—whenever a caller needs Straits Times section headlines—but it provides no explicit guidance on when not to use it or how it compares to alternatives. The 'one public section' constraint gives some context, but no alternative tools are mentioned, leaving usage mostly inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.