Fetch News18 top stories from the public feed; returns headline items from the general top-story stream. For a section-specific list, use news18_headlines with a supported section slug. Use news18_article with a returned article URL when you need one story's body.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations already carry the safety profile, so the bar is lower. The description adds the useful scoping fact that results come from the general top-story stream and are headline items (not story bodies), but says nothing about update cadence, item counts, or pagination.
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?
Three tight sentences with the core purpose front-loaded and the two routing cues following. Every sentence earns its place by preventing a mis-selection of a sibling tool.
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?
With zero params, an output schema covering return values, and annotations covering safety, the description is essentially complete for correct invocation. Minor gap: no note on freshness or result volume for a live news feed.
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?
Zero parameters and 100% schema description coverage, so parameter semantics are moot and the baseline of 4 applies. There is correctly no parameter prose, since there is nothing to describe.
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 and resource ('Fetch News18 top stories') and immediately delimits scope ('general top-story stream', not a section feed). It cleanly distinguishes itself from news18_headlines and news18_article without the agent needing to open either sibling's schema.
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?
Gives explicit routing: use this for the general top-story stream, use news18_headlines with a section slug for section-specific lists, and use news18_article with a returned URL for a single story's body. Both alternatives and the conditions that select them are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
