radarr_delete_customfilter

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

The annotations already declare destructiveHint=true and readOnlyHint=false. The description adds no new behavioral context beyond restating the destructive nature, such as irreversibility, permission requirements, or cascade effects. It is consistent with annotations but provides no additional transparency.

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 with two sentences. The first sentence efficiently states the tool's action. The second sentence repeats the destructive annotation, which is somewhat redundant but still serves as a clear warning. Overall, it is well-structured and front-loaded.

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 annotations and an output schema, the description is adequate. It covers the core behavior and destructiveness. It does not describe return values, but the output schema exists. It lacks details about prerequisites or error handling, but these are less critical given the tool's simplicity.

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 has one required parameter 'id' (integer), but schema description coverage is 0%. The description does not explain that 'id' refers to the custom filter to delete. Although 'id' is self-explanatory in context, the description offers no added meaning, failing to compensate for the low schema coverage.

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 the specific verb 'Delete' and resource 'custom filters', clearly distinguishing it from sibling tools like radarr_create_customfilter, radarr_update_customfilter, radarr_get_customfilter, and radarr_list_customfilter. The purpose is unambiguous.

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 context is clear: this tool is for deleting custom filters. While no explicit exclusions or alternatives are mentioned, the verb+resource combination makes the intended use obvious. For a simple delete operation, the guidance is sufficient.

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