Retrieve Birmingham Mail top stories from its public home RSS feed. Skips photo galleries without readable article bodies.
Get Birmingham Mail top stories. Returns fresh Birmingham Mail top stories from the public home RSS feed. Photo galleries are omitted because they have no readable article body.
| 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 it returns fresh stories from a public RSS feed, which implies no authentication needed, and notes that photo galleries are omitted due to lack of readable article body, providing useful behavioral context beyond the schema.
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 sentences, front-loaded with the core purpose and then a concise note about exclusions. No wasted words.
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 parameterless tool with no output schema, the description is complete enough: it tells the agent the source, that it's fresh, and what's omitted. Minor gaps like return format are not critical for a simple feed fetch.
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?
Given there are zero parameters, the schema coverage is 100% vacuously. The description adds context about the data source (public home RSS feed) and scope, which is helpful even though no parameters exist.
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 it fetches Birmingham Mail top stories from the public home RSS feed, with a specific verb 'Get' and resource. It also explicitly excludes photo galleries, distinguishing its scope.
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?
It indicates this is for top stories from the home feed, and mentions the alternative of excluding galleries, but does not explicitly name sibling tools or when to use them. The context of being a news feed is clear, but exclusions are not comprehensive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.