Fetch current Evening Standard top stories with titles, URLs, summaries, publication times, authors, and images. No parameters needed; use standard-headlines for a single section.
Get Evening Standard top stories. Returns the current Evening Standard top stories. Each item has its title, URL, summary, publication time, author and image. Takes no parameters; use standard-headlines for a single section.
| 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?
No annotations are provided, so the description carries the full burden. It usefully discloses the returned fields (title, URL, summary, publication time, author, image), which is valuable given there is no output schema, but it says nothing about auth needs, rate limits, or freshness/update behavior.
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?
Front-loaded with the purpose and ends with the alternative routing. The first two sentences are near-redundant ('Get... top stories' / 'Returns the current... top stories'), a minor waste of space.
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 read tool with no output schema, the description covers purpose, routing, and return fields adequately. Remaining gaps are minor freshness/behavioral details rather than anything needed to invoke it correctly.
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, so the baseline is 4. The description confirms 'Takes no parameters,' which is consistent with the empty schema and removes any doubt about required input.
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 ('Get Evening Standard top stories') and distinguishes itself from the sibling standard_headlines by contrast. An agent can identify this as the top-stories endpoint without opening anything else.
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?
Names an alternative explicitly ('use `standard-headlines` for a single section'), giving a selection condition. The routing is slightly ambiguous since it doesn't clarify how 'top stories' differs from the headlines/sections siblings, but clear context is present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.