Delete Rear_port

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

Beyond annotations (destructiveHint=true), the description explains cascading deletes, irreversibility, and the HTTP 204 response. This provides critical behavioral context that annotations alone lack.

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?

Six sentences, each adding value. Front-loaded with purpose. Includes essential warnings without verbosity. Minor improvement possible by merging the cascading examples into a more general statement.

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?

For a one-parameter delete tool with no output schema, the description covers input, behavior, and output sufficiently. Could mention that the object must exist, but it's implied by the delete action.

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 parameter 'id' already described. The description adds no new semantic information beyond confirming it's a numeric id, so baseline 3 is appropriate.

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 begins with a clear verb+resource: 'Delete a rear_port from NetBox by numeric id.' It uniquely identifies the action for this specific object type among many sibling delete tools.

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 states 'Confirm the exact object — and what will cascade with it — with the user before calling.' This provides clear when-to-use guidance and warns against casual use, differentiating it from non-destructive tools.

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