Retrieve Entertainment Weekly headlines by section slug. Returns fresh titles from one public section, including TV, movies, and music.
Get Entertainment Weekly section headlines. Returns fresh headlines from one public Entertainment Weekly section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Entertainment Weekly section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden. It conveys a read-only, low-risk operation via 'Returns fresh headlines' and 'public,' which is useful context. However, it does not mention rate limits, result shape, pagination, or any other behavioral caveats, so its transparency is adequate but not thorough.
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, focused sentences: the first states the action and resource, the second adds useful scope and freshness details. There is no filler or redundant restatement of the schema.
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 single-parameter tool with a fully enumerated section slug, the description plus schema is sufficient for an agent to select and invoke the tool correctly. It could be more complete with an explicit pointer to sibling tools such as ew_news or ew_sections, and it does not describe the return format, but neither gap blocks correct usage.
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 input schema already covers the single parameter 100%, including an enum of valid section slugs and a description. The description's 'one public Entertainment Weekly section' reinforces the parameter's role but does not add meaningful semantics beyond the schema, so the baseline score of 3 applies.
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 states a specific verb ('Get') and resource ('Entertainment Weekly section headlines'), and clarifies scope with 'from one public Entertainment Weekly section.' It does not explicitly name sibling alternatives like ew_news, ew_article, or ew_sections, so differentiation must be inferred rather than stated.
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 when to use the tool — when you need fresh headlines from a specific Entertainment Weekly section — but it provides no explicit when-to-use versus when-not-to-use guidance and names no alternatives. Selection among ew_headlines, ew_news, and ew_sections is left to the agent's inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.