update_series_quality

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

There are no annotations, so the description itself must disclose behavior. It does this well by explaining that only provided fields are changed and omitted fields remain untouched. The HTTP PATCH method and accepted quality values add useful behavioral context beyond a simple update statement.

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 concise, front-loaded with the core purpose, and uses the space efficiently. The quality value list is long but necessary because those values are not otherwise represented as enums in the schema.

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?

The definition provides enough context for an agent to call the tool: endpoint, required and optional parameters, valid values, and partial update behavior. It does not detail auth requirements or return values, but the tool has no output schema and this is likely a simple mutation, so these are not critical 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?

The schema already covers all parameter descriptions, but this is a case where the description adds real value by listing the valid quality strings, since there are no enums in the schema. It also clarifies that provided fields are merged with existing values rather than replacing the whole config.

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 clearly states it updates allowed and/or preferred qualities for an existing series, identifies the specific PATCH endpoint, and this distinguishes it from sibling tools like update_release_groups. The verb and resource are specific and unambiguous.

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 clearly frames the usage context: updating quality settings for an existing series via PATCH. It also clarifies partial update behavior, which is essential for correct use. It does not explicitly name alternatives, but the scope is clear enough that an agent can select this tool without much inference.

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