show_activity_feed

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses that results are merged from ALL saved shows, sorted newest-first, and that the default is 3 episodes per show. It does not mention read-only status or request cost, but the read-only nature is strongly implied and no mutation claims are made.

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?

The description is two sentences with no filler. It front-loads the core behavior, adds a clear value proposition, and states the key default without unnecessary detail.

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?

The description plus the fully documented input schema provides enough context for an agent to call the tool correctly. There is no output schema, but the description clearly communicates that the result is a chronological feed of episodes, which is sufficient for this aggregated read tool.

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 is 100%, so the parameters are already well documented. The description adds a small amount of context by restating the eps_per_show default and emphasizing the aggregate nature, but it does not materially expand on the schema parameter meanings.

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 clearly states the resource (recent episodes across all saved shows) and the operation (a merged, chronological feed sorted newest-first). It distinguishes itself from single-show episode tools by emphasizing the cross-library aggregation and 'one scroll instead of N show visits'.

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 conveys the intended use case: seeing the latest episodes across all saved shows in a single view. It provides clear context for when to choose this tool, though it does not explicitly name alternative tools or state when not to use it.

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