Lenny's Podcast MCP

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

No annotations are provided, so the description carries the full burden. It mentions listing 'all available episodes/guests,' which implies a read-only operation, but doesn't disclose behavioral traits such as pagination, rate limits, authentication needs, or what 'available' means (e.g., published status). The description adds minimal context beyond the basic action.

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, front-loaded with the core purpose and followed by a usage hint. Every sentence adds value: the first defines the action, and the second provides context. There is no wasted text, making it efficient and well-structured.

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?

Given the tool's complexity is low (0 parameters, no output schema), the description is somewhat complete but lacks depth. It covers the basic purpose and a hint on usage, but without annotations or output schema, it doesn't fully address behavioral aspects like response format or limitations, leaving gaps for an AI agent.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied as it adequately handles the lack of parameters without introducing confusion.

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 tool's purpose: 'List all available episodes/guests in Lenny's Podcast archive.' It specifies the verb ('List') and resource ('episodes/guests'), though it doesn't explicitly differentiate from sibling tools like 'get_episode' or 'search_transcripts' beyond mentioning 'to see what guests and topics are available to search.'

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 implies usage context: 'Use this to see what guests and topics are available to search.' This suggests it's for initial exploration before more specific actions, but it doesn't explicitly state when to use this tool versus alternatives like 'search_transcripts' or 'get_episode,' nor does it provide exclusions or prerequisites.

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