Recently updated feeds

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint and destructiveHint as safe, so the description adds useful behavioral context: newest-activity-first ordering and the differentiation between updated feeds and new shows. This goes beyond what the schema and annotations convey, though it leaves exact recency windows unspecified.

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 concise sentences front-load the core behavior and ordering, then give the sibling distinction and usage guidance. Every sentence earns its place without redundancy or 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?

This is a simple, read-only list tool with fully documented optional parameters and safety annotations. The description tells the agent what the result means conceptually, how it is ordered, and when to use the main alternative. No critical call-invocation information is missing.

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 description coverage for all 5 parameters is 100%, so the schema carries the full parameter documentation burden and the baseline is 3. The description only loosely contextualizes 'published something recently' and adds no parameter-specific semantics beyond the schema.

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 action ('Feeds that published something recently, newest activity first') and explicitly distinguishes this tool from get_new_feeds by clarifying that it tracks updates rather than new shows. An agent can immediately tell which tool to use among the many feed-related siblings.

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?

It explicitly says 'Use get_new_feeds for shows that are new to the index', providing direct when-not/alternative guidance. It also explains the conceptual context of feeds vs shows, so an agent knows when this tool is relevant.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.