sonarr_create_metadata

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

The description adds the explicit warning 'WRITE: this modifies your Sonarr instance,' which clarifies the write nature beyond the annotations' readOnlyHint=false. However, it doesn't disclose potential side effects like duplicate creation 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 only two sentences and avoids unnecessary text. It is efficient, though the second sentence primarily restates the write nature rather than adding new actionable context.

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 create operation with a generic body schema and no parameter descriptions, the description is insufficient. It lacks details on required fields, configuration structure, or response interpretation, even though an output schema exists.

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 has 0% description coverage, and the description says nothing about the 'body' or 'force_save' parameters. An agent receives no information about what fields to include in the body or how force_save behaves.

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 clearly states 'Create metadata providers,' identifying the specific verb and resource. It doesn't explicitly differentiate from sibling tools like sonarr_create_metadata_action, but the object is clearly metadata providers.

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 sonarr_create_metadata_action, sonarr_create_metadata_test, or sonarr_create_metadata_testall. The WRITE warning is a behavioral note, not usage guidance.

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