Fetch Entertainment Weekly top stories from its homepage, returning fresh stories as clean JSON for news tracking or aggregation.
Get Entertainment Weekly top stories. Returns fresh Entertainment Weekly stories from its homepage.
| 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 discloses that it returns fresh stories from the homepage, giving some behavioral context. But it does not specify the output structure (e.g., list of titles vs. full text) or any pagination/limits, which is a notable gap for a no-schema 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?
Two short sentences with the key action front-loaded. The slight redundancy of 'top stories' and 'fresh stories' is minor; there is no wasted content.
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?
The tool is simple with no parameters and no output schema. The description explains the purpose and source sufficiently for an agent to select and invoke it correctly. It could mention the return format, but that is typically covered by an output schema when present, so the gap is acceptable here.
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 coverage is 100% trivially. The description adds no parameter meaning, but none is needed. Baseline 4 for zero parameters is appropriate.
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 'Get' and resource 'Entertainment Weekly top stories', and clarifies the source as the homepage with a freshness qualifier. This clearly differentiates it from sibling tools like ew_article, ew_author, and ew_headlines.
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?
The description implies usage for fetching fresh EW top stories, providing clear context. However, it does not explicitly mention alternative tools (e.g., ew_article for specific articles) or exclusion conditions, so routing guidance is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.