Erase a Device's Configuration

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

Annotations only say destructiveHint=true; the description adds the material details an agent actually needs — write erase semantics, auto-answered prompts, the fact that the running config is NOT saved before reload, and that the operation is irreversible. It also mandates a confirmation protocol before invoking.

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?

Front-loaded with the action, then the CRITICAL safety gate, then examples — each block earns its place with no filler. The confirmation instruction is exactly the kind of content worth spending tokens on for an irreversible operation.

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?

A destructive two-parameter tool with an output schema and adequate annotations: the description covers what is destroyed, irreversibility, prompt handling, and the required user-confirmation step. Nothing an agent needs to invoke it safely is missing.

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?

Coverage is 50%: 'name' is documented in the schema, while 'reload' has no schema description. The description compensates by explaining that reload is on by default and what that means (device boots blank), implying reload=false skips the reboot, though it never states that case explicitly.

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 and resource ('Erase a Cisco device's startup-config ("write erase")') plus the default reload behavior, which cleanly separates it from save_device_configuration, get_device_configuration, and delete_device_from_network.

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?

Explains the intended scenario ('the classic way to reset lab gear') and gives two concrete invocation examples, and states that prompts are auto-answered. It does not explicitly contrast with siblings like delete_device_from_network or configure_device, so a 4 rather than a 5.

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