radarr_update_qualitydefinition

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description reinforces that this is a write operation, but adds limited new behavioral context beyond what annotations state.

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 very brief with no redundancy. However, brevity comes at the cost of essential information, so it's not a fully effective use of that conciseness.

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 description is insufficient for an agent to know what to put in the body, how to obtain the id, or what response to expect. The output schema exists, but input semantics are absent. More context is needed, especially given the nested object parameter.

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 0% and the description doesn't explain the 'id' or 'body' parameters. The body is a free-form object with additionalProperties: true, leaving the agent without guidance on required fields or structure.

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 quality definitions and flags it as a write operation. However, it doesn't distinguish from the sibling tool radarr_update_quality_definitions (plural), which may create ambiguity.

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 context is provided. It doesn't mention that a corresponding list/get tool exists or clarify when to use this singular update vs. the plural update_quality_definitions sibling.

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