sonarr_list_episodefile

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

The description only restates the tool name and adds no behavioral context beyond the readOnlyHint annotation. It does not disclose that series_id and episode_file_ids can filter results, nor does it mention pagination or output characteristics. However, it does not contradict the annotation.

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 a single short sentence that is easy to parse and front-loads the verb. It is concise but also under-specifies, though that issue is captured elsewhere.

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?

For a tool with two optional parameters and an output schema, the description is far too minimal. It omits any explanation of filtering semantics, and given the 0% schema coverage, the agent has no information about how to use the parameters effectively.

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 zero description coverage and the description does not mention either parameter. The agent cannot infer what series_id or episode_file_ids mean from the description alone, making parameter understanding entirely dependent on names.

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 action (list) and resource (episode files), making the core purpose unambiguous. It does not explicitly distinguish itself from sibling tools like sonarr_get_episodefile, but 'list' implies a collection-level operation.

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 about when to use this tool versus alternatives like sonarr_get_episodefile or sonarr_list_episode. There is no mention of filtering options or scenarios where this tool is appropriate.

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