list_episodes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the GET endpoint and the fact that it returns metadata, but does not describe response structure or any rate limits. Given the annotations, the description provides minimal additional behavioral context, which is acceptable but not rich.

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, includes the HTTP method and path, and lists parameters in a clear block. It is front-loaded with the main action. However, it could be more structured by explaining parameter interactions, but as a short definition it is efficient.

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 existence of many sibling list_episodes_* tools, this description is incomplete. It does not clarify whether the tool returns all episodes when no parameters are provided, or whether at least one parameter is needed. It also does not specify what 'metadata' includes beyond the schema's output. For a tool with two optional parameters and an output schema, more guidance is needed to avoid ambiguity.

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 0%, so the description must compensate. It provides brief explanations: 'Series IDs to list episodes for' and 'Episodes ID to list'. This adds meaning, but lacks detail on whether both can be used together, if at least one is required, or the format of the IDs. For a tool with zero schema coverage, the parameter documentation is insufficient.

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 lists episode metadata and can filter by series or episode IDs. It uses a specific verb ('List') and resource ('episodes metadata'). However, it does not differentiate from sibling tools like list_episodes_history or list_episodes_wanted, which might also return episode-related data.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies you provide seriesid or episodeid but does not explain when you would choose this over other list_episodes_* tools. No explicit when-to-use or when-not-to-use instructions.

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