Retrieve current India Today headlines by section slug from one hub page, delivering structured JSON for news monitoring, research, or content curation.
Get India Today section headlines. Returns current headlines from one India Today section hub page.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | India Today section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses that results are 'current' and limited to one section hub page, which clarifies dynamic scope and avoids implying site-wide aggregation. However, it does not describe output fields, failure behavior, pagination, or any limits beyond 'headlines.'
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 two short sentences with no filler or redundant elaboration. The second sentence earns its place by adding 'current' and 'from one India Today section hub page,' giving the agent concrete behavioral 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?
For a one-parameter enum-driven headline tool, the description plus schema is mostly sufficient to invoke it correctly. However, with no output schema and no annotations, the description leaves the return shape vaguely defined and gives no indication of pagination, count, or error behavior.
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 lone parameter has an enum plus the description 'India Today section slug.' The tool description adds no additional meaning about the parameter, so the baseline score 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 states a clear verb ('Get') and resource ('India Today section headlines'), and narrows scope by specifying 'from one India Today section hub page.' It is easily distinguishable from article/author tools, though it does not explicitly differentiate itself from sibling headline tools such as indiatoday_news or indiatoday_sections.
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 offers no explicit when-to-use guidance, exclusions, or alternatives. An agent must infer from the name and schema when this tool should be chosen over the many sibling headline/section tools, and no context is given about cases where another tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.