sonarr_create_qualityprofile

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

The description adds no behavioral context beyond the provided annotations. 'WRITE: this modifies your Sonarr instance' is a redundant restatement of readOnlyHint=false and does not disclose any failure modes, required fields, or effects of creating a profile.

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?

While the description is short, it is not effectively concise: the second sentence duplicates annotation information and adds no value. The entire description is under-specified for a tool with a complex body parameter.

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 requiring an opaque body, the description is severely incomplete. It does not mention how to discover the required fields (e.g., via the quality profile schema endpoint) or provide any guidance on the structure of the 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 input schema has a single opaque `body` object with additionalProperties=true and 0% description coverage. The description provides no information about what fields to include, leaving the agent completely in the dark about how to construct the request.

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 states 'Create quality profiles' which is a specific verb and resource, clearly distinguishing this create operation from sibling list/get/update/delete tools for quality profiles.

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 use this tool or how it relates to alternatives like the schema endpoint. The WRITE warning merely restates the annotation, and no prerequisites or recommended workflow are mentioned.

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