sonarr_create_releaseprofile

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds 'WRITE: this modifies your Sonarr instance', which explicitly calls out that the operation mutates local state. This is a minor addition beyond the annotation, but it doesn't disclose any other behavioral details like required authentication or effects on existing profiles.

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 two sentences, front-loading the action and adding a brief warning. It is appropriately minimal with no wasted words.

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?

The tool is a create operation with a complex, undocumented body schema and no output documentation. The description fails to explain what a release profile is, what fields are required, or what the expected response is. An agent would be left guessing 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 input schema has a single 'body' parameter with additionalProperties:true and zero description coverage. The description provides no explanation of what fields the body should contain, what values are valid, or how to structure the payload. This is a free-form body with no guidance, making it difficult for an agent to invoke correctly.

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 the specific verb 'Create' and resource 'release profiles', clearly distinguishing it from sibling tools like list_releaseprofile, update_releaseprofile, and delete_releaseprofile. The addition of 'WRITE' further clarifies its 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 or any alternatives. It doesn't mention prerequisites, when to prefer this over updating an existing profile, or any exclusions.

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