create_settings_radarr

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

Annotations already indicate this is a non-read, idempotent, non-destructive operation, so the description's burden is lower. However, the description adds no behavioral context beyond 'Create' – no mention of side effects, validation, or what happens on repeated calls.

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 compact and front-loaded, with the core purpose in the opening sentence and a useful pointer to the schema endpoint. The endpoint line is somewhat redundant with the name, but there is no filler.

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?

For a create operation with an open-ended body and no parameter documentation, the description leaves the agent knowing how to find fields but not what the operation needs or how it relates to the sibling test/update/delete tools. The output schema covers return shape but not request semantics.

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%, so the description must compensate for the open body object. It only labels body as 'Request payload' and points the agent to the GET/schema endpoint; it does not describe any expected Radarr fields, defaults, or required configuration values.

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 states a clear action and resource: 'Create Radarr instance.' It is specific enough to distinguish from unrelated tools and from settings for Sonarr, but it does not explicitly address the close sibling create_settings_radarr_test or explain what a Radarr instance represents.

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?

There is no guidance about when to use this tool instead of alternatives such as create_settings_radarr_test for validating a connection or update_settings_radarr_by_radarr_id for modifying an existing instance. The only advisory content is to read the GET/schema endpoint before supplying the body, which is a pre-call instruction rather than usage selection guidance.

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