sonarr_create_metadata_action

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

The description says 'WRITE: this modifies your Sonarr instance,' which adds no information beyond the annotation readOnlyHint=false. It doesn't disclose any additional behavioral traits such as effects on existing metadata, permission requirements, or failure modes. Since the annotation already covers the write aspect, the description 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 short, which is good for conciseness, but the second sentence merely restates the annotation and does not contribute useful information. It is not under-specified to the point of 'Process,' but it could be better structured to include meaningful details without adding bulk.

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?

While the tool has annotations and an output schema, the description lacks essential context about what a 'metadata action' is, how to construct the 'body', and what the action does. The agent cannot determine correct invocation from this description, especially given the large set of sibling tools.

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 input schema has zero descriptions for the parameters 'name' and 'body'. The description does not explain what these parameters mean, what format 'body' should take, or what values are valid. With 0% schema coverage, the description entirely fails to compensate, leaving the agent guessing about parameter usage.

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 simply restates the tool name ('Create metadata action') without explaining what a metadata action is or how it differs from sibling tools like sonarr_create_metadata or sonarr_create_metadata_test. The verb and resource are present, but the resource is undefined, making it a tautology rather than a clear purpose.

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 provided about when to use this tool versus other metadata-related tools. It doesn't mention prerequisites, intended use cases, or alternatives, leaving the agent without any basis for selecting it from the many sibling tools.

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