Delete Circuit_group_assignment

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

Describes destructive and irreversible nature, cascading deletes with concrete examples, and the HTTP 204 response. This goes well beyond the annotations (destructiveHint: true) by explaining specific behaviors and consequences.

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, front-loads the purpose, and efficiently covers the warning, explanation, and response in just a few sentences. Every sentence adds value.

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 a simple delete operation with one parameter and no output schema, the description fully covers what the tool does, its risks, and the expected response. No additional context is needed.

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 single parameter 'id' is already fully described in the schema ('Numeric id of the circuit_group_assignment to delete'). The description adds no new semantic information beyond restating that deletion is by numeric id.

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 'Delete a circuit_group_assignment from NetBox by numeric id', specifying the verb and resource. It distinguishes from the many sibling delete tools by naming the specific object type.

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?

Explicitly advises to confirm with the user before calling due to irreversibility and cascading deletes, providing clear context on when to use. However, it does not mention alternative tools (e.g., get or list) for verification.

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