sonarr_trigger_rename_series

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

No annotations are provided, so the description carries the full burden. It states the action ('rename episode files') but does not disclose that this is a mutating operation with potential irreversible effects, does not mention auth requirements, and does not describe the return value. The 'omit to rename all' detail is already in the schema, adding no new behavioral context.

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?

Two sentences, front-loaded with the main purpose, no filler words. Every sentence earns its place.

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 tool is simple (1 optional param, no output schema), and the description covers purpose and param usage. However, the absence of annotations and output schema means the description should ideally mention what the command returns and any side effects; it does not, leaving some gap.

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?

Schema coverage is 100% (the single param seriesIds has a description). The tool description repeats the param behavior ('omit to rename all') but adds no additional meaning beyond the schema, so it meets the baseline for high schema coverage.

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 uses the specific verb 'Rename' and identifies the resource 'episode files on disk', clearly distinguishing this from sibling tools like sonarr_refresh_series or sonarr_trigger_rescan_series. The purpose is unambiguous and precise.

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?

The description provides clear context: it renames files to match Sonarr naming settings. It explains how to scope the operation ('Pass specific seriesIds or omit to rename all'), but does not explicitly exclude alternatives or name related tools, so it stops short of a full guideline.

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