radarr_update_collection

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

The description restates mutation ('WRITE: this modifies your Radarr instance') which is already implied by annotations (readOnlyHint=false). It adds no additional behavioral details such as side effects, required access permissions, or consequences of modifying a collection.

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 and front-loaded with the verb, but it is under-specified. The WRITE clause is somewhat redundant given annotations, yet it serves as a safety reminder. Overall, it is brief but lacks substance.

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?

Despite having an output schema, the description offers minimal context. It does not mention what data should be in the body, how to identify the collection, or any relationship to other collection-related tools. This is insufficient for a write operation with a free-form payload.

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%, and the description does not explain the 'id' or 'body' parameters. The body is a free-form object with additionalProperties=true, and without any explanation of expected fields or structure, the agent cannot effectively construct input.

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 names the action ('Update') and resource ('movie collections'), identifying it as a write operation. However, it does not distinguish from the sibling tool 'radarr_update_collections' (plural), leaving ambiguity about singular vs. bulk updating.

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 guidance is provided about when to use this tool versus alternatives like 'radarr_get_collection' or 'radarr_update_collections'. The only extra signal is the WRITE warning, which concerns caution rather than usage context.

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