sonarr_bulk_update_episodefile

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

The description adds 'WRITE: this modifies your Sonarr instance,' which is already implied by readOnlyHint=false. It provides no additional behavioral context such as what fields are updated, whether properties are overwritten, or potential side effects.

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 front-loaded, with each sentence conveying a piece of information. However, it borders on under-specification, and the second sentence adds little beyond what annotations already tell the agent.

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?

The description is far too incomplete for a bulk update operation. It lacks details about the request body, affected episodefile properties, error handling, and any output. The presence of an output schema does not compensate for the missing input semantics.

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 only parameter 'body' has no description in the schema, and the description doesn't explain its structure or content. With 0% schema description coverage, the agent is left without any information about what the array should contain.

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 the verb 'update' and the resource 'episodefile' and indicates bulk operation. However, it does not distinguish this tool from the similarly named sibling 'sonarr_bulk_edit_episodefiles', leaving ambiguity about the exact scope.

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, such as sonarr_update_episodefile for single updates or sonarr_bulk_edit_episodefiles. The WRITE warning is not a usage guideline; it only reiterates the mutation.

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