radarr_create_tag

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

Annotations already declare readOnlyHint=false, so the 'WRITE' note merely restates redundant information. The description adds no new behavioral context such as required permissions, idempotency, or side effects beyond what annotations provide. It does not contradict the annotations, but adds minimal value.

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 concise, using only two short sentences. 'Create tags' front-loads the action, and the 'WRITE' warning adds essential safety information. No unnecessary words or repetition appear, and the structure is straightforward.

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?

Despite having an output schema, the description fails to explain the required request body structure for the 'body' parameter, which is a free-form JSON object. The tool is simple, but without input guidance, the description is incomplete for 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?

With zero schema description coverage and no parameter documentation in the description, the 'body' parameter remains completely undefined. The agent cannot infer what fields or structure are needed to create a tag, making the tool effectively unusable without external knowledge.

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 'Create tags' uses a specific verb and resource, clearly indicating the tool's function. It also distinguishes from sibling tools like radarr_update_tag, radarr_delete_tag, and radarr_list_tag by specifying creation. The explicit 'WRITE' note 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 provides no guidance on when to use this tool versus alternatives such as radarr_update_tag or radarr_delete_tag. It only states the basic action without context or exclusions, leaving the agent without decision-support information.

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