radarr_update_releaseprofile

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

The description says 'WRITE: this modifies your Radarr instance,' which aligns with annotations (readOnlyHint=false) and explicitly confirms a write operation. However, it adds no additional behavioral context such as side effects, idempotency, authorization requirements, or what fields are affected—leaving the agent with minimal insight beyond the annotations.

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 short and front-loaded: 'Update release profiles. WRITE: this modifies your Radarr instance.' It is concise and direct. However, the 'WRITE' phrase duplicates information already available in the annotations, so a small deduction is warranted.

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 tool is an update operation with a nested body object and minimal schema documentation, the description provides insufficient context for an agent to understand the update semantics, required ID, or how to structure the body. The output schema doesn't offset the input-side ambiguity.

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 compensate. It fails to explain that 'id' likely refers to the release profile identifier or that 'body' should contain the updated profile fields. With nested objects and an open-ended body schema, the description offers no help for constructing a valid request.

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 'Update release profiles,' which is a specific verb+resource and clearly distinguishes from sibling tools like list/get/create/delete release profiles. However, it essentially restates the tool name without elaborating on what an update entails, so it stops short of a perfect score.

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. The description does not mention related CRUD operations, prerequisites, or typical use cases. The 'WRITE' warning is a behavior notice, not usage direction.

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