Fetch irish Independent public editorial or RSS sections accepted by irishindependent_headlines. Use irishindependent_headlines with a returned slug for section stories. Use irishindependent_news for the general feed.
| 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?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is known. The description adds that sections are 'public editorial or RSS' and relates them to headlines slugs, but does not describe return shape, ordering, or rate limits.
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 no filler, and the primary purpose is front-loaded before the routing advice. Nothing redundant, though the opening sentence's phrasing is slightly clunky.
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 no input params and an output schema present, the description need not explain return values. It covers purpose, workflow dependencies, and the alternative feed tool, leaving only minor unspecified details like ordering.
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 takes zero parameters, so the baseline is 4. There are no arguments whose meaning the description could clarify, and it correctly implies the tool is a no-arg catalog fetch.
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 (Fetch) and resource (Irish Independent public editorial or RSS sections), and implicitly distinguishes from siblings by naming headlines and news. The phrase 'accepted by irishindependent_headlines' is slightly awkward but conveys that returned slugs feed other tools.
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?
Explicitly routes the agent: use irishindependent_headlines with a returned slug for section stories, and irishindependent_news for the general feed. Both the follow-up path and the alternative tool are named with their selection conditions.
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.
