organize_season_folders

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

No annotations are present, so the description fills the burden reasonably. It discloses that the action moves all downloaded episode files, preserves original filenames, enables season folders, and also moves associated subtitled/other files. It does not add notes about irreversibility or downstream effects, but the core behavior is clear.

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 front-loaded with a one-line command, then branches into a short 'Maybe this' bullets list and the exact API call. It is compact and effectively structured, though the second paragraph partly re-explains the first by saying it enables season folders and moves all downloaded files.

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 one-parametically tool with an output schema and no annotations, the description gives the operation, the endpointBody, scope, and typical usage conditions. The only meaningful gap is the under-specified series_slug value, but an agent can infer enough to invoke it correctly. This is complete enough to act on autonomously.

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 required string, series_slug, with a 0% description coverage, so the description must carry the meaning. The endpoint line 'series/{slug}' and the repeated use of 'series' imply that series_slug is the series identifier, but the description never explicitly states the expected format or how the slug is obtained. Partial but not full compensation.

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 starts with a precise verb-plus-resource statement: 'Move episodes into Season XX/ subdirectories without renaming files.' It further specifies that original filenames are prserved and associated files like subitles are moved too, so an agent can clearly picture exactly what the operation does and how it differs from a rename/organizer.

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 includes a explicit 'Use this when' list with three concrete signals: flattened multi-season directories, Plex missing episodes due to multi-season-in-one-folder, and a late second season. It does not state when not to use it or name an alternative sibling, so it stops short of full 5.

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