radarr_update_tag

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

The description adds 'WRITE: this modifies your Radarr instance,' which is consistent with readOnlyHint:false but redundant. It provides no additional behavioral details such as partial vs. full updates, required permissions, or side effects, so transparency is limited.

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 extremely short but under-specified. The second sentence about WRITE adds little value because the annotation already communicates the write nature. It is not concise in a meaningful way; it just omits necessary information.

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 mutation tool with an unspecified body object and no parameter documentation, this description is insufficiently complete. Even though an output schema exists, the lack of input parameter explanations and usage guidance leaves significant gaps for the agent.

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%, yet the description offers no information about the 'id' or 'body' parameters. The agent is left without any guidance on what the body should contain or what values are valid, making parameter semantics almost entirely absent.

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 tags' which is a clear verb+resource, but it is vague and doesn't distinguish from sibling operations like create_tag or delete_tag. It also doesn't specify that it updates a single tag by ID, so the purpose is only minimally clear.

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 on when to use this tool instead of alternatives. It doesn't mention that create_tag should be used for new tags or that this is for modifying existing tags, providing no context for tool selection.

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