sonarr_delete_qualityprofile

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

Annotations already declare destructiveHint=true. The description merely restates this as 'DESTRUCTIVE: this deletes data' without adding new behavioral context such as irreversibility, associated record cleanup, or failure conditions if the profile is in use. It adds no information beyond the annotation.

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 extremely concise, consisting of two short sentences. Every word earns its place: the first states the action, the second reinforces the destructive nature. No fluff or redundancy.

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?

Given the simplicity of the operation (a single-id delete), the annotations (destructiveHint), and the presence of an output schema, the description is adequate. It lacks explicit usage guidance, but for a straightforward delete tool, the information provided is largely sufficient.

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 does not explain the 'id' parameter. While the parameter name is self-explanatory in context, the description adds no semantic detail about what the id refers to or constraints on it, so it fails to compensate for the missing schema documentation.

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 verb 'Delete' and the resource 'quality profiles', directly matching the tool name and distinguishing it from CRUD siblings like get/update/create. It leaves no ambiguity about the tool's function.

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 on when to use this tool versus alternatives such as bulk delete or disabling profiles. The description lacks any context on prerequisites, edge cases, or explicit 'do not use if' scenarios.

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