Fetch Salon's top stories, including titles, URLs, summaries, publication times, authors, and images. No parameters needed.
Get Salon top stories. Returns Salon's latest top stories across the site. Takes no parameters, and salon-headlines narrows by section instead. Each item has its title, URL, summary, publication time, author and image.
| 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 provided, the description carries the burden and does well: it discloses that the tool takes no parameters (safe read, no configuration), that it returns a site-wide feed, and enumerates the item fields (title, URL, summary, publication time, author, image). It stops short of stating pagination or result limits, but covers the essentials for a read-only list 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?
Three short sentences, each earning its place: purpose, sibling differentiation, and return shape. Purpose and scope are front-loaded with no filler.
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?
With no output schema, the description compensates by listing the returned fields, and it explains the parameter situation and sibling relationship. Complete enough to call correctly; only pagination/limits are left unstated.
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?
There are zero parameters, so the baseline is 4. The description correctly notes the absence of parameters, confirming there is no hidden filtering to supply.
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 Salon top stories") and clarifies scope ("latest top stories across the site"). It explicitly distinguishes itself from the sibling salon_headlines, so an agent can route correctly without opening a schema.
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 the alternative (salon-headlines) and the condition that selects it (narrowing by section), which is exactly the routing information an agent needs. It does not spell out a when-not-to-use case beyond that, but the guidance is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.