remove_static_lease

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

Discloses effects beyond annotations: irreversibility, config save, device staying online, possibly receiving a different dynamic IP. DestructiveHint=true is confirmed and expanded with the exact consequences and recovery path.

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?

Every sentence is functional: action, irreversibility, network consequence, prerequisite, and routing to alternatives. Front-loaded primary action, no filler.

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 destructive command, description covers prerequisites, consequences, alternatives, and recovery. Output schema exists, so return-format documentation is not required. Nothing an agent needs to call this 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?

Input schema already fully documents the MAC parameter (100% coverage) with format and case-insensitivity, so description adds little about semantics. The instruction to find the exact MAC through list_static_leases adds value but baseline 3 applies because schema covers the parameter definition.

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 the action precisely: 'Delete the static DHCP reservation for a MAC and save the router config.' Names the resource (static DHCP reservation) and differentiates from siblings by referencing set_static_lease and list_static_leases. An agent knows exactly what operation this performs.

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 instructs to 'Use list_static_leases to find the exact MAC first' and warns 'To move a device to another IP, call set_static_lease/pin_device directly instead of removing first.' This gives clear when-to-use, prerequisites, and exclusions.

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