radarr_create_tag

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description contributes nothing further: no note on whether the tag persists server-side, what happens on duplicate labels, or error behavior when the Radarr instance is unreachable.

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?

A single short sentence with the verb front-loaded and no filler. Nothing in it is wasted given the tool's simplicity.

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 one-parameter create tool with annotation coverage and no output schema, this is minimally sufficient. It still leaves open whether duplicates are rejected and what identifier comes back, which an agent calling a create endpoint would benefit from knowing.

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 coverage is 100% and the single 'label' parameter is documented as 'Tag label' in the schema, so the baseline of 3 applies. The description adds no meaning beyond that, such as format constraints or whether the label must be unique.

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?

States a specific verb+resource ('Create a new Radarr tag'), which the agent can distinguish from radarr_get_tags, radarr_update_tag, radarr_delete_tag and from sonarr_create_tag. It stops short of describing what a tag is used for or what creation returns, but the operation itself is unmistakable.

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 on when to create a tag versus reusing existing ones via radarr_get_tags, nor any mention of preconditions such as label uniqueness or required indexer connection. The agent is left to infer the workflow entirely.

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