cleanuparr_delete_arr_instance

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

The description only restates the delete action, which is already captured by the destructiveHint annotation. It does not disclose whether deletion is permanent, cascades to related data, or requires any confirmation. This adds no value beyond the annotation.

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?

At just eight words, the description is extremely concise and front-loaded with the action verb. Every word is necessary, with no redundant filler.

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 a simple delete operation, and the destructiveHint annotation plus output schema provide some context. However, the description fails to explain the arr_type parameter and lacks usage details such as prerequisites or consequences, leaving gaps in context.

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 no descriptions (0% coverage), and the description only clarifies that instance_id is a GUID. It does not explain arr_type values or their allowed range. With no enum constraints, the agent is left guessing what arr_type should be.

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 explicitly states the action ('Delete'), the resource ('*arr instance'), and the identifier ('by GUID'), clearly distinguishing it from sibling tools like create_arr_instance, update_arr_instance, or list_arr_instances.

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 when-to-use or alternative guidance is provided. The context implies this tool is for deleting an *arr instance, but the description doesn't mention any exclusions or prerequisites. Since it is the only delete tool for arr instances, usage is reasonably implied.

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