Retrieve top stories from Dawn (Pakistan) via its public RSS feed, returning clean JSON for news aggregation, monitoring, and analysis.
Get Dawn top stories. Returns fresh Dawn (Pakistan) stories from the public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool returns fresh stories from a public RSS feed, indicating a read operation with no auth likely. However, it does not describe the output structure, pagination, or any potential rate limits, leaving some behavioral aspects undisclosed.
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 concise sentences, front-loaded with the primary purpose. There is no wasted text.
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 tool, the description states what it returns but lacks detail on the format or structure of the stories. Given no output schema, a bit more detail on the returned items would improve completeness.
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 has zero parameters, so the description correctly adds no parameter-specific semantics. Per the baseline for 0-parameter tools, the description is adequate.
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 the tool fetches Dawn top stories, specifying the source (Pakistan) and feed type (public RSS). This is a specific verb+resource description that distinguishes it from sibling tools like dawn_article (which fetches a specific article) and dawn_headlines (which might fetch headlines only).
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 provides no guidance on when to use this tool versus its siblings (e.g., dawn_headlines, dawn_article). It does not mention alternatives or exclusions, leaving the agent to infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.