update_release_groups

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

With no annotations, description carries full burden. It reveals PATCH method and partial update behavior. However, lacks details on side effects, permissions, rate limits, or error handling. Provides basic parameter behavior but not comprehensive for a mutating tool.

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?

Concise and well-structured: brief summary followed by parameter descriptions. No unnecessary words. Front-loaded with purpose and key behavior.

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?

Given an output schema exists, return value details are unnecessary. The description covers action and parameters adequately. Minor omission: no guidance on error responses or conditions, but overall sufficient for a focused mutation tool.

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 description coverage is 0%, but description fully explains each parameter with examples and context (e.g., 'series_slug: Series slug (e.g. "tvdb1234")', 'fallback_groups: Anime release group fallback list (in priority order)'). This adds significant meaning beyond 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?

Clearly states 'Update release group configuration for a series', specifying verb, resource, and scope. The HTTP method and endpoint are provided for exact context. Distinguishes from sibling 'diagnose_release_groups' which is for analysis.

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?

States that only provided fields are changed (partial update), which guides usage. However, does not explicitly mention when to use versus alternatives or prerequisites. Context is clear but lacks exclusions.

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