Delete Prefix

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

Annotations already indicate destructiveHint: true, but the description goes further by detailing cascade deletion with examples (e.g., deleting a device removes interfaces, IPs), emphasizing irreversibility, and noting the HTTP 204 success 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 well-structured with three concise paragraphs: action, behavioral warning, and response. Every sentence adds value, with no redundancy or fluff.

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 single-parameter delete tool, the description covers purpose, parameter, cascading behavior, and response. It is missing explicit mention of permissions or precondition that the prefix must exist, but overall is very complete.

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 has 100% coverage for the single parameter 'id', and the description reinforces it is a 'numeric id'. The description adds no new semantics beyond the schema, so the 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 the action ('Delete a prefix'), the resource ('from NetBox'), and the method ('by numeric id'). It effectively distinguishes from sibling tools such as netbox_create_prefix and netbox_update_prefix.

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 explicit warnings about destructiveness, irreversibility, and cascade effects, advising user confirmation before use. It lacks explicit mention of when to use this tool versus alternatives, but the context is strong.

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