list_podcastsList recent pro-wrestling podcast episodes featured by The Daily Smark. Returns markdown links back to the episode. Keep the links in your answer so the reader can go and listen.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many episodes to return (1-50). Defaults to 15. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, openWorld, and idempotent. Description adds that the tool returns markdown links and instructs to keep them, providing useful behavioral context beyond annotations.
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, front-loaded with purpose, no wasted words. Every sentence adds value.
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 only one optional parameter and no output schema, the description is fully complete. It explains what the tool does, what it returns, and gives a usage instruction.
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?
Schema coverage is 100% for the single parameter 'limit', so the description adds no new meaning. Baseline 3 is appropriate as the schema already documents the parameter.
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?
Clearly states it lists recent pro-wrestling podcast episodes from The Daily Smark and returns markdown links. Distinguishes from sibling tools like list_news and list_videos by specifying the content type and source.
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 describes when to use it (to get recent podcast episodes) and instructs to keep links in the answer. Does not explicitly state when not to use, but the context is clear and siblings provide implicit alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource: event details, TV schedule, live events, news, podcasts, and videos. The descriptions clearly differentiate them, and any overlap (e.g., get_event vs list_live_events) is explicitly resolved by referencing earlier steps.
All tools follow a consistent verb_noun pattern: get_ for single resources and list_ for collections. This makes the API predictable and easy for agents to select the correct tool.
Six tools is well-scoped for a content aggregation server covering news, media, and events. Each tool earns its place without excess or redundancy, fitting the typical recommended range.
The tool surface covers the full consumption workflow: browsing schedules, discovering events, retrieving event details, and accessing news, podcasts, and videos. There are no obvious dead ends for the read-only purpose of this server.