delete_network_device

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

With no annotations, the description carries the full burden. It usefully discloses the default preview mode and the confirm toggle, which is meaningful behavioral context for a destructive tool, but it omits whether deletion is permanent/reversible, cascading effects, and any auth requirements.

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?

Two short, front-loaded sentences with zero waste; the action and the key safety mechanism are both stated up front.

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?

An output schema exists, so return-value documentation is unnecessary. For a simple 2-parameter delete tool the description covers the core mechanics, though additional safety context (irreversibility) would round it out.

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 0%, so the description must compensate. It effectively explains both parameters: 'by its ID' documents device_id's purpose and 'confirm=true' documents the boolean's effect, adding semantics the bare schema lacks.

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?

States a specific verb (Remove) and resource (one device from the network table), making it distinguishable from siblings like remove_client, remove_dhcp_lease, or remove_domain. The phrase 'network table' is slightly loose but clearly ties to the network-devices resource implied by list_network_devices.

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 sentence 'Preview unless confirm=true' gives real operational guidance on how to trigger the actual deletion versus a dry run. However, there is no explicit statement of when this tool is appropriate versus alternatives, nor prerequisites.

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