radarr_update_delayprofile

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

The description explicitly labels this as 'WRITE' and states it modifies the Radarr instance, which adds a clear side-effect warning. However, it does not disclose other behavioral traits like whether the operation is a partial or full update, or whether the target profile must already exist. Annotations already indicate readOnlyHint=false, so the description adds only a small amount beyond the structured data.

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?

Two short sentences with no redundant content: the first states the purpose, the second warns of the side effect. Every word earns its place and the structure is front-loaded.

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 simple update tool, the description is sparse. The schema has a free-form body object with additionalProperties true, and the description does not clarify what fields are expected or whether the update is partial or full replacement. The output schema exists, so return format is covered externally, but the request semantics are under-specified.

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 schema provides no descriptions (0% coverage). The description only says 'Update delay profiles' and does not explain the 'id' and 'body' parameters, their formats, or which fields body should contain. This leaves the agent to guess that 'id' identifies the profile and 'body' carries the update payload.

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 'Update delay profiles' uses a specific verb ('Update') and resource ('delay profiles'), clearly distinguishing it from sibling tools like create_delayprofile, delete_delayprofile, and list_delayprofile. The additional 'WRITE' label reinforces the action.

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?

The description implies usage for modifying existing delay profiles but provides no explicit guidance on when to use it versus create/delete/reorder alternatives, nor any prerequisites or exclusions. The purpose itself is enough to infer the basic use case.

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