sonarr_refresh_series

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

With no annotations, the description carries the full behavioral burden. It does say the tool pulls from metadata sources and updates episode/air-date data, but it doesn't say whether this is a blocking or queued/async operation, whether it requires the series to already exist, whether it can fail on unavailable metadata providers, or how long it takes.

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 short sentences front-loaded with the core action; nothing is padded. The trailing 'etc.' is mildly vague but costs 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 single-parameter, no-output-schema tool this is close to adequate, but key operational facts (sync vs. queued, error behavior on metadata failure) are absent and there are no annotations to fill the 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?

Only one parameter exists ('seriesId') and the schema already documents it fully at 100% coverage ('Sonarr series ID to refresh'). The description adds no additional semantics about identifier format or origin, so the baseline 3 applies.

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?

States a specific verb and resource ('Refresh series information from metadata sources') and names the effect ('Updates episode info, air dates'), which distinguishes it from siblings like sonarr_edit_series and sonarr_rescan_series. It doesn't explicitly contrast itself with those siblings, so it stops short of a 5.

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 and no alternatives are named, despite two nearby siblings (sonarr_rescan_series, sonarr_edit_series) that an agent could easily confuse with this one. The implication that this is for syncing metadata is left to inference.

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