sonarr_rescan_series

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

There are no annotations, so the description carries the full behavioral burden. It discloses that it checks for new, modified, or deleted files, but does not state whether the operation is synchronous or asynchronous, what permissions are required, whether it triggers a command/job, or any side effects or rate limits.

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 tightly written sentences that are front-loaded with the core action and then a clarifying detail. No wasted words.

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-parameter, no-annotation tool, the description is minimally adequate in saying what it does. However, it leaves out critical context such as how it differs from sonarr_refresh_series and whether it is an async command, which an agent would need to select it correctly.

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% and the single parameter's meaning ('Sonarr series ID to rescan') is fully documented in the schema. The description adds nothing beyond the schema for parameter semantics, so the baseline of 3 is appropriate.

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 a specific verb and resource ('Rescan series folder for files') and clarifies what it checks ('new, modified, or deleted episode files'). It is clear what the tool does, but it does not differentiate itself from the close sibling sonarr_refresh_series, which likely also triggers series folder updates.

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 when-to-use guidance is given. It does not mention prerequisites, alternatives (e.g., sonarr_refresh_series), or exclusions, leaving the agent to infer when this tool should be chosen over similar siblings.

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