radarr_delete_notification

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

The description repeats the destructive nature already captured by the destructiveHint annotation without adding new behavioral context. It does not explain consequences like irreversibility or the exact scope of data removed, so it adds minimal value beyond the structured annotations.

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 very concise with two short sentences. The first sentence is essential; the second sentence contains a redundant warning already present in the annotations, slightly reducing efficiency but not causing bloat.

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 operation with one parameter and annotations indicating destructiveness, the description is sufficiently complete. It clearly states the action and resource, and the parameter is straightforward, though it could benefit from noting the id's purpose.

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?

With 0% schema description coverage, the description fails to elaborate on the 'id' parameter. Although it is inferable that the id refers to a notification provider, the description does not clarify the format, source, or required context for the parameter.

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 a specific verb 'Delete' and identifies the resource 'notification providers', making the action unambiguous. It clearly distinguishes from sibling tools like create/update/get notification by specifying the deletion operation.

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 implies the tool should be used to delete notification providers, but it does not explicitly state when to use it versus alternatives or provide any exclusionary guidance. There is no mention of prerequisites or cautionary notes beyond the destructive warning.

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