sonarr_delete_releaseprofile

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

The description repeats the destructiveHint annotation with 'DESTRUCTIVE: this deletes data' but adds no additional behavioral context. It does not explain irreversibility or impacts beyond what the annotation already conveys.

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 concise at two sentences, but the second sentence is redundant with the destructiveHint annotation. 'Delete release profiles' is front-loaded and efficient.

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 simple delete tool with annotations providing safety context and an output schema present, the description is minimally adequate. However, it lacks any context about return values or the need for a valid existing ID, making it incomplete for an agent fully self-serviced.

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 contains only an integer parameter 'id' with 0% description coverage. The description does not clarify that 'id' refers to the release profile identifier, leaving the parameter's meaning implicit.

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 the tool's action: 'Delete release profiles.' The verb 'delete' and resource 'release profiles' are specific and distinguish this from sibling tools like sonarr_get_releaseprofile or sonarr_update_releaseprofile.

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. It does not mention prerequisites, potential effects, or scenarios where deletion is appropriate.

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