List RetailMeNot seasonal and holiday deal events, including Black Friday and Cyber Monday, with slugs for /retailmenot/deal-event.
List RetailMeNot seasonal deal events. Returns RetailMeNot's seasonal and holiday deal events (for example Black Friday, Cyber Monday, Back-to-School) with slugs for /retailmenot/deal-event.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose what comes back (seasonal/holiday events plus slugs), which is genuinely useful. However, it says nothing about read-only semantics, result ordering, seasonality scoping (current vs. all-time events), or pagination/limits.
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, front-loaded with the action and resource. Slight redundancy between 'seasonal deal events' and 'seasonal and holiday deal events', but overall tight and free of 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?
No output schema exists, so the description must convey the return shape, and it does: a list of named seasonal events with slugs. For a zero-parameter listing tool this is close to sufficient, with only scope/ordering details 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?
The tool takes zero parameters, so the schema has nothing to explain and the description has no parameter semantics to clarify. Baseline 4 applies; no documentation is missing because no inputs exist.
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 ('List RetailMeNot seasonal deal events') and enumerates examples (Black Friday, Cyber Monday, Back-to-School). It also hints at the relationship to the singular sibling by noting the returned slugs feed '/retailmenot/deal-event', though it never explicitly names retailmenot_deal_event as its companion.
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?
Usage is only implied: an agent can infer this is the discovery step before calling retailmenot_deal_event with a slug, but the description never states when to use this versus retailmenot_categories, retailmenot_stores, or the singular deal-event tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.