cleanuparr_delete_notification_provider

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

The annotation destructiveHint=true already indicates destructiveness. The description 'Delete' is consistent with this annotation but adds no further behavioral context such as irreversibility, cascading effects, or authorization requirements. No contradiction exists.

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 a single concise sentence (7 words) that directly states the action. It is front-loaded with the verb and resource, with no extraneous information.

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 deletion tool with a destructive annotation and an output schema, the description is mostly complete. It identifies the resource and parameter. However, it omits potential caveats like irreversibility or behavior when the provider does not exist, which would add helpful context but is not strictly required.

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 offers no parameter description (0% coverage). The description partially compensates by indicating 'by GUID', which gives meaning to the provider_id parameter, but it does not explain where to obtain the GUID or validate its existence. Some benefit is provided beyond the bare schema.

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 action ('Delete') and the resource ('notification provider'), with an identifier method ('by GUID'). This distinguishes it from sibling delete tools like cleanuparr_delete_arr_instance and cleanuparr_delete_download_client by specifying the resource type.

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 such as create/update/test notification providers. It is implied that one uses it to delete a provider, but there are no explicit usage contexts, prerequisites, or exclusions.

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