Delete Contact_assignment

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

The description adds critical context beyond the destructiveHint annotation: details about NetBox cascading deletes (e.g., deleting a device removes interfaces, power ports, assigned IPs) and confirms HTTP 204 response. No contradiction with annotations.

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 efficiently structured: a brief opening sentence, then important warnings, examples, and response info. Every sentence adds value without redundancy.

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, the description covers the action, cascading risks, user confirmation requirement, and response. No output schema exists, but the description adequately addresses what the agent needs to know.

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?

Only one parameter (id) with 100% schema coverage. The description states 'numeric id', which mirrors the schema. No additional semantic information beyond what the schema provides.

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?

Clearly states 'Delete a contact_assignment from NetBox by numeric id.' The verb, resource, and method are explicit. Differentiates from other delete tools by naming the specific resource.

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?

Warns that the operation is destructive and irreversible, explains cascading deletes with concrete examples, and instructs to confirm with the user before calling. Provides clear when-to-use and when-not-to-use guidance.

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