radarr_delete_releaseprofile

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

Annotations already declare destructiveHint=true, and the description adds 'DESTRUCTIVE: this deletes data' which is slightly redundant but reinforces the risk. No additional behavioral details are provided (e.g., irreversibility, effects on associated data).

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?

Extremely concise: two short sentences, front-loaded with the action and followed by a clear warning. Every word earns its place.

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 simple and has an output schema, so return values are documented elsewhere. However, the description lacks context about prerequisites (e.g., id must exist) and consequences beyond generic destructiveness, leaving gaps for an agent.

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 one parameter 'id' (integer) but the description does not explain what the id refers to (i.e., the release profile ID). With 0% schema description coverage, the description provides no semantic help, forcing the agent to infer from the tool name.

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 'Delete release profiles' uses a specific verb (delete) and resource (release profiles), clearly distinguishing it from sibling tools like create/update/list/get. The additional destructive warning reinforces the 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?

No explicit guidance on when to use this tool versus alternatives. It doesn't mention that the 'id' parameter should come from list/get operations, nor does it state that it's for removing existing profiles only. The context is minimal.

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