Fetch fresh headlines from any Hindustan Times section by providing its slug. Covers India, world, business, sports, entertainment, and more.
Get Hindustan Times section headlines. Returns fresh headlines from one public Hindustan Times section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Hindustan 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 carries the full burden of behavioral disclosure. It adds minimal context ('fresh', 'public') but fails to mention return format, pagination, rate limits, or any failure modes, leaving the agent uncertain about the exact output.
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 sentences, no filler, and the core action is front-loaded. Every word contributes to the tool's purpose.
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?
The tool is simple (one enum parameter) but has no output schema. The description says 'returns fresh headlines' without specifying whether they are plain strings, objects with metadata, or how many are returned. It is adequate for basic selection but leaves the result shape undefined.
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% because the 'section' parameter has a description ('Hindustan Times section slug') and an enum of valid values. The tool description adds no additional parameter-specific meaning, so the baseline of 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 uses a specific verb ('Get') and resource ('Hindustan Times section headlines') and clarifies it returns fresh headlines from one public section. This clearly differentiates it from sibling tools like hindustan_times_sections (which likely lists sections) and hindustan_times_article (which fetches full articles).
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 guidance is given on when to use this tool versus alternatives such as hindustan_times_news or hindustan_times_sections. The description only states what it does, not when to select it among the many headline/news tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.