list_episodefile

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat that. However, the description adds no additional behavioral context, such as pagination, authentication, or output format. It only states the HTTP method and path, which is trivial and already implied by 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 extremely brief and contains no fluff, which is concise. However, it is under-specified: it lacks critical details about the tool's behavior and parameters. The structure is a simple sentence followed by a list, which is functional but not front-loaded with the most important information.

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 filter parameters and an output schema, the description is inadequate. It does not clarify that it returns a list of episode files, how the filters interact, or any default behavior. The description would force an agent to infer the tool's purpose from the name and endpoint, which is insufficient for correct usage.

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 has no descriptions (0% coverage), so the description is the only source of parameter meaning. It only says 'Query parameter' for each parameter, which is redundant with the schema's type. It does not explain that series_id filters by series or that episode_file_ids filters by specific file IDs, leaving the agent without any semantic understanding.

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 states a verb ('Read') and a resource ('EpisodeFile'), but it is ambiguous whether this is a list or single-item operation. The tool name 'list_episodefile' implies listing, but the description does not explicitly say it lists multiple files, nor does it distinguish from 'get_episodefile_by_id'. It provides no specificity beyond a generic read action.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it returns a list, that series_id filters by series, or that episode_file_ids filters by specific IDs. It also does not point to sibling tools like 'get_episodefile_by_id' for single-file retrieval.

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