Sonarr: Mark History Failed

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

Describes the trigger effect (re-search on next interval) and return behavior (confirmation, no body from API). Annotations indicate destructiveness and idempotence; description adds context without contradiction.

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?

Three concise sentences: action, consequence, return value. No repetition or filler. Front-loaded with the primary purpose.

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 tool with annotations and no output schema, the description fully explains what it does, when to use it, and what to expect as a result. No gaps.

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 covers the single 'id' parameter with description. The description adds useful context about its source ('from sonarr_history or sonarr_history_series'), but this is supplementary to the schema.

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?

Description clearly states the action ('Mark a Sonarr history entry as failed') and the resource type. It distinguishes from sibling tools like sonarr_queue_regrab by specifying the context of wrong cut/quality/release.

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?

Provides a clear use case: 'Useful when an episode imported as the wrong cut/quality/release.' Does not explicitly mention when not to use or alternatives, but the context is strong enough for typical scenarios.

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