Netbox Bulk Delete Objects

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

Annotations already disclose destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds crucial value: it specifies 'Permanently' (irreversible) and 'in a single transaction' (atomicity), which goes beyond the annotations. The 'Confirm with the user first' instruction is an important behavioral directive.

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?

Two short imperative sentences, front-loaded with the core action and a critical safety instruction. No 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?

Given the destructive nature, output schema presence, and full parameter coverage, the description covers the essentials: permanence, atomicity, and user confirmation. It could mention rate limits or partial failure behavior, but those are minor for a delete tool.

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?

Schema description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional parameter details, but the baseline for high coverage is 3. It earns a 4 because the 'single transaction' phrasing clarifies the atomic expectation for the object_ids batch, slightly augmenting parameter semantics.

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 states a specific verb (delete), resource (objects), scope (many objects of one type), and execution model (single transaction). It cleanly distinguishes itself from netbox_delete_object (singular) and netbox_bulk_update_objects.

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?

It gives a clear operational precondition ('Confirm with the user first'), which is valuable context for a destructive operation. However, it doesn't explicitly name alternatives like netbox_delete_object for single deletions, leaving the choice between bulk and single deletion to inference.

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