radarr_update_customfilter

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds an explicit 'WRITE:' warning and states it modifies the Radarr instance, which reinforces the non-read-only nature but doesn't disclose additional behavioral details such as whether the update is partial or full replacement, or any permission requirements. It adds minimal context 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 two short sentences with front-loaded purpose and a clear write warning. No filler or redundant repetition.

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?

The tool has an output schema and annotations that cover safety flags, but the description lacks guidance on constructing the body parameter and doesn't mention the relationship to listing/getting custom filters. For a simple update operation with a nested body object, more detail is needed to ensure correct invocation.

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 defines id (required) and body (object) with no descriptions; schema description coverage is 0%. The description does not explain what id represents or what the body should contain, leaving the agent to infer the semantics from the tool name. It fails to compensate for the schema's lack of detail.

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 custom filters' with a specific verb (update) and resource (custom filters), clearly distinguishing it from sibling tools like create_customfilter, delete_customfilter, and get_customfilter. It is concise and unambiguous.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of how to obtain the required id. The only additional sentence is a generic write warning, which doesn't help select the tool.

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