sonarr_bulk_edit_episodefiles

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

Annotations already indicate readOnlyHint=false, so the description's 'WRITE: this modifies your Sonarr instance' merely restates the annotation. No additional behavioral context is provided, such as what fields are affected, whether changes are reversible, or any side effects. Since no extra value is added beyond the annotations, the score is low.

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 to the point, but the phrasing 'Update episodefile editor' is awkward and unclear. It is not well-structured for clarity, though it is concise. The write warning is an extra sentence that adds little.

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 bulk edit operation with a complex body parameter and no schema descriptions, the description is severely incomplete. It fails to convey the tool's purpose, the required body structure, or any operational context. The output schema exists but doesn't compensate for the lack of behavioral and parameter guidance.

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 one parameter 'body' with zero schema description coverage. The description provides no information about what the body should contain, expected fields, or format. With 0% coverage, the description was expected to compensate but does not, leaving the agent completely in the dark about parameter usage.

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 'Update episodefile editor' is vague and fails to clearly state what the tool does. It does not specify that it performs a bulk edit of episode files, and the phrase 'episodefile editor' is confusing. The write warning is not a purpose statement and does not distinguish this tool from siblings like sonarr_bulk_update_episodefile.

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 only warns that it modifies the Sonarr instance, which is not a usage guideline. There are many sibling tools with similar names, and no mention is made of when bulk edit is appropriate.

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