Fetch up to 30 top E! News stories from the US edition with titles, URLs, summaries, publication times, bylines, and thumbnails.
Get E! News top stories. Returns up to 30 top stories from the US edition of E! News. Each item has its title, canonical article URL, summary, publication time, byline and thumbnail. Takes no parameters; use eonline-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?
With no annotations, the description carries the full burden and does well: it discloses the item cap (up to 30), the edition (US), the no-parameter nature, and the field shape of each return item. It stops short of covering auth needs, rate limits, or freshness/refresh behavior, so it is not fully comprehensive, but it is markedly richer than typical.
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?
Two sentences, fully front-loaded: purpose and scope first, return contents second, routing note last. No filler or repetition of the tool name.
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?
No output schema exists, so the description must describe returns itself — and it does, itemizing title, canonical URL, summary, publication time, byline and thumbnail. Combined with the count cap and routing hint, an agent needs nothing else to call this 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 reinforces this explicitly ('Takes no parameters'), which is the only useful statement available for a parameterless tool.
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 E! News top stories') and immediately narrows scope to top stories from the US edition, which cleanly separates it from eonline_article, eonline_author and eonline_sections.
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 names the alternative ('use `eonline-headlines` for a single section') and pairs it with the condition that selects it, so the agent knows when to route elsewhere without inspecting any sibling schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.