episodes_by_feed_id

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

The description labels the tool as read-only (consistent with the readOnlyHint annotation) and does not contradict any annotations. However, it adds no additional behavioral context beyond 'get episodes', such as pagination, error handling, or rate limits. With annotations present, the bar is lower, and a neutral score is appropriate.

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 that efficiently convey the core purpose and a key prerequisite. There is no extraneous content, and critical information is front-loaded.

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 simplicity (no output schema, straightforward parameters) and the presence of annotations, the description is nearly complete. It covers the main function and a prerequisite. However, it lacks details on default pagination (max default 10) or how to interpret the response, but this is minor for a fetch 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?

The input schema already provides thorough descriptions for all four parameters (100% coverage). The description does not add new semantic information about the parameters beyond what the schema provides, though it reinforces that 'id' is the feed ID. Baseline 3 is warranted.

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 it gets episodes for a specific podcast by feed ID. The verb is specific and the resource is discrete. However, it does not explicitly differentiate from sibling tools like recent_episodes or search_by_term, which could also return episodes but with different selection criteria.

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 a prerequisite: use podcast_by_feed_url first to get the feed ID. This is helpful guidance. However, it does not mention when to use alternatives, such as recent_episodes for broader queries, or when not to use this tool (e.g., if no feed ID is known).

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