delete_episodefile_by_id

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

The annotations already communicate destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds no behavioral context beyond the endpoint—such as whether the file on disk is permanently removed, whether confirmation is needed, or what happens to associated data. It does not contradict the annotations.

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 short and front-loaded with the core action. The endpoint line and Args line are mildly redundant with the tool name and schema, but there is no filler or unnecessary prose.

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 simple single-parameter delete operation, the strong annotations cover the safety profile and idempotency adequately. However, the description omits any mention of side effects, the bulk alternative, or when this tool is appropriate, so an agent has to infer some context from the tool name.

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 only provides that id is a required integer. The description adds that id is a path parameter, which is useful for invocation. However, it does not explain what the id represents beyond what is already obvious from the tool name and endpoint.

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 begins with 'Delete EpisodeFile', a clear verb and resource that states what the tool does. Including 'DELETE /api/v3/episodefile/{id}' reinforces that this operates on a single episode file by ID, though it does not explicitly distinguish itself from the sibling delete_episodefile_bulk tool.

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 given about when to use this tool versus delete_episodefile_bulk or other related deletion tools. The description only provides the endpoint and parameter, with no context about prerequisites, alternative routes, or conditions that should trigger this tool.

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