radarr_create_metadata

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

Annotations already declare readOnlyHint=false, and the description merely restates this as 'WRITE: this modifies your Radarr instance.' It adds no additional behavioral context such as side effects, reversibility, or permission requirements.

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 compact and front-loaded with the purpose. It contains no fluff, though the second sentence is a mild redundancy with annotations. It is appropriately sized for a simple statement, but is too short for the needed detail.

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?

With an output schema present, return values need not be described, but the input parameters are entirely undocumented. For a create tool with a free-form body, the description is critically incomplete and fails to provide any context on how to construct a valid request.

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 schema description coverage is 0%, and the description provides no explanation for 'body' or 'force_save'. The body parameter is a free-form object with additionalProperties true, making it impossible to know what content is expected. The description does not compensate at all.

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 specific verb 'Create' and the resource 'metadata providers', clearly distinguishing it from sibling tools like radarr_update_metadata or radarr_list_metadata. The purpose is 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?

No guidance is given on when to use this tool versus alternatives. The 'WRITE' warning is not usage guidance; it does not mention prerequisites, alternatives like radarr_list_metadata, or when creating is appropriate.

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