Delete Power_outlet

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

The description goes well beyond the 'destructiveHint' annotation by detailing cascading delete behavior with concrete examples (device, site, manufacturer) and states HTTP 204 response. This provides rich behavioral context for safe usage.

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 with two paragraphs, front-loads the purpose, and uses clear formatting. Every sentence adds value, making it efficient and easy to parse.

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 simple delete tool with one parameter, the description covers the operation, cascading effects, need for confirmation, and response format. It is fully complete and leaves no significant gaps.

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 input schema is simple (one integer 'id' with description) and has 100% coverage. The description does not add further semantic details about the parameter beyond what the schema already provides, so a baseline score of 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 clearly states 'Delete a power_outlet from NetBox by numeric id' with a specific verb and resource. However, it does not explicitly differentiate this tool from other delete tools in the sibling list, such as netbox_delete_site or netbox_delete_device, beyond the resource name.

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 provides clear guidance to confirm the exact object and cascading effects with the user before calling. It warns about destructiveness and irreversibility but does not name explicit alternatives or when-not-to-use scenarios.

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