radarr_delete_autotagging

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description's 'DESTRUCTIVE: this deletes data' merely repeats the annotation and adds no new behavioral information such as permanence or permission requirements.

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 concise and front-loaded with the verb and resource. However, the second sentence is redundant with the destructiveHint annotation, so it could be shorter without losing 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?

Given the minimal schema and annotations, the description is incomplete for an agent needing to invoke the tool correctly. It lacks any indication that id is the auto-tagging rule identifier, how to obtain it, or the result of deletion. The output schema exists, but the description doesn't clarify the expected input.

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) with zero description coverage, and the description does not explain what id refers to or how to find it. No parameter semantics are provided beyond the schema's data type.

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 'auto tagging rules', which exactly matches the tool name and distinguishes it from sibling delete tools like delete_tag or delete_customfilter.

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 or how it relates to alternatives. It does not mention that the rule ID should come from list_autotagging, nor does it contrast with create/update autotagging.

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