radarr_update_customformat

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

The description's 'WRITE: this modifies your Radarr instance' adds a human-friendly warning, but it largely restates the annotation readOnlyHint=false. No additional behavioral details are disclosed, such as whether updates overwrite existing fields, require existing formats, or have side effects.

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 concise, with only two sentences. The WRITE warning is somewhat redundant with the annotation, but the overall length is appropriate and front-loaded with the core purpose.

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 an update tool with a loosely defined 'body' object and sparse schema, the description is incomplete. It does not explain expected fields, reference the schema tool, or clarify single vs. bulk updates, leaving significant 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 provides zero information about the 'id' or 'body' parameters. The agent is left without any understanding of what payload to send or how the id is used, making this 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 uses a clear verb ('update') and resource ('custom formats'), making the basic purpose understandable. However, it does not differentiate from sibling tools like radarr_bulk_update_customformat, so it is not fully distinguishing.

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 (e.g., create, bulk_update, delete). The 'WRITE' warning is not usage guidance; it simply states the operation modifies the instance.

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