Delete Inventory_item_role

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

Annotations already indicate destructiveHint=true. The description adds critical context: the operation is irreversible, NetBox cascades deletes (with concrete examples), and there is no undo. It also notes the HTTP 204 response. This goes well beyond annotations, providing rich behavioral disclosure.

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: a clear purpose statement, followed by a well-structured paragraph about destructive behavior and cascading, then a brief note on the response. Every sentence serves a purpose, and the formatting aids readability.

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 tool's complexity (destructive, cascading deletes, single parameter), the description is complete. It covers the operation, behavior, confirmation needed, and return value. No output schema exists, but the description adequately describes the response.

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 coverage is 100% with one required integer id. The description does not add meaningful semantics beyond restating that the id is numeric. With full schema coverage, the baseline is 3, and the description adds no extra value.

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 'Delete a inventory_item_role from NetBox by numeric id.' It identifies the specific verb (delete) and resource (inventory_item_role), clearly distinguishing it from sibling delete tools for other resources.

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 warns that the operation is destructive and irreversible, mentions NetBox cascading deletes with examples, and advises confirming the object and cascade effects with the user before calling. While it does not explicitly say when not to use it, the caution implies it should only be used after careful user confirmation.

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