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 of behavioral disclosure. It mentions retrieving a 'full transcript' but doesn't specify if this is a read-only operation, what format the transcript is in (e.g., text, JSON), or any potential limitations (e.g., availability, error handling). For a tool with no annotation coverage, this lacks critical details about how it behaves 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 concise and front-loaded, with the core purpose stated in the first sentence and usage guidance in the second. Both sentences are relevant and add value, avoiding redundancy. It could be slightly more structured by explicitly separating purpose from guidelines, but it's efficient overall.

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 low complexity (1 parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and some usage context but lacks details on behavioral aspects (e.g., output format, error cases) that would help an agent use it effectively. Without annotations or output schema, more elaboration would improve completeness.

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 schema description coverage is 100%, with the single parameter 'guest' well-documented in the schema as 'The name of the guest (e.g., 'Shreyas Doshi', 'Julie Zhuo').' The description adds minimal value beyond this, only reiterating 'by guest name' without providing additional context like examples or constraints. This meets the baseline for high schema coverage.

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: 'Get the full transcript for a specific episode by guest name.' It specifies the verb ('Get'), resource ('full transcript'), and key constraint ('by guest name'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'list_episodes' or 'search_transcripts' beyond implying this is for a 'specific episode,' which is why it doesn't achieve a perfect score.

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 provides some usage guidance with 'Use this when you want to dive deeper into a specific conversation,' which implies this tool is for detailed exploration rather than listing or searching. However, it doesn't explicitly state when not to use it or name alternatives (e.g., 'list_episodes' for overviews or 'search_transcripts' for broader queries), leaving room for ambiguity in tool selection.

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