Fetch Khaleej Times top stories from its public Google News sitemap, skipping video, partner, and section pages for clean headline results.
Get Khaleej Times top stories. Returns fresh Khaleej Times top stories from its public Google News sitemap (the site publishes no RSS feed). Video, partner-content, and section pages are left out.
| 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 disclosure burden. It usefully reveals the source is a public Google News sitemap and that video, partner-content, and section pages are excluded, which is meaningful behavioral context. However, it does not describe the return format, number of stories, ordering, or update latency, leaving some behavioral uncertainty for a fetch tool.
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 compact: one sentence for the core purpose and one sentence for source and content filtering. There is minor repetition of 'top stories' between the first and second sentences, but no filler or irrelevant detail.
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?
This is a simple zero-parameter list-fetch tool with no output schema, so the stakes are low. The description covers what it returns, which source it uses, and what it leaves out. It does not specify the output shape or freshness interval, but those omissions are minor for a top-stories fetcher.
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 and the schema is empty, so there is nothing the description needs to explain about parameters. The baseline of 4 applies for no-parameter tools, and the description adds no misleading parameter information.
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 specific verb and resource: 'Get Khaleej Times top stories,' and adds a concrete source (public Google News sitemap) and exclusions (video, partner-content, section pages). It does not explicitly name or differentiate from sibling khaleejtimes_headlines, which could also return news/headlines, so it stops short of a full 5.
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?
Usage context is implied: use this for a list of top stories, not for a specific article or sections. The 'publishes no RSS feed' note explains the source choice but does not say when to prefer this tool over khaleejtimes_headlines, khaleejtimes_article, or khaleejtimes_sections, nor does it provide explicit when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.