radarr_update_quality_definitions

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

Annotations already indicate readOnlyHint=false. The description's 'WRITE: this modifies your Radarr instance' essentially restates that. It adds no extra context about side effects, whether definitions are replaced wholesale, or any required permissions. Minimal additive value.

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 two short sentences with the core action front-loaded. The second sentence, while somewhat redundant given annotations, is a clear warning and doesn't add fluff. It is appropriately concise.

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 the empty schema and lack of sibling differentiation, the description is inadequate. It doesn't clarify that this likely updates multiple definitions (plural) or what the body structure looks like. The output schema is present, so return value details are not needed, but the request context is missing.

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 input schema has only a 'body' array with no item structure or description (0% schema coverage). The description does not explain what the body should contain, leaving the agent completely uninformed about the required payload. This is a critical gap.

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 a specific action ('Update quality definitions') on a specific resource. It also warns that it is a write operation. However, it does not differentiate between this tool and the singular sibling 'radarr_update_qualitydefinition', nor does it explain what 'quality definitions' encompass.

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 on when to use this tool versus alternatives like the singular 'update_qualitydefinition'. The WRITE warning is about side effects, not usage context. There is no mention of prerequisites, typical scenarios, or exclusions.

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