router_manage_dhcp_reservation

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

No annotations are provided, so the description carries the full burden. It usefully discloses that confirm is needed for mutations and that force bypasses a 'Network Guard safety check' — a meaningful behavioral signal. But it omits the effects of the operations (whether deleting a reservation disrupts a connected client, whether changes take effect immediately, permissions required), which matters for a write tool.

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?

A single front-loaded purpose sentence followed by a compact arg list; no filler. The Args block is slightly mechanical (repeating parameter names the schema already has) but each line adds constraint information.

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 values need not be explained, and all parameters are described. What's missing is mutation-side context: no warning about disruption, no explanation of Network Guard's purpose, and no indication of reversibility or ordering constraints — gaps that matter for a destructive-capable tool with zero annotations.

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 description coverage is 0%, so the description must compensate, and it does describe all five parameters with per-action conditionality and an example MAC format. It stops short of specifying IP format constraints or what 'confirm' actually gates, but the coverage is far better than the schema alone.

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 names a specific resource (static DHCP IP address reservations) and enumerates the three operations (add, delete, list), which lets an agent know exactly what domain it operates in. 'Manages' is a somewhat generic verb, but the Args block immediately disambiguates it into concrete actions.

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?

It gives the action values and states which parameters are required per action (mac for add/delete, ip for add), which is real usage guidance. However, it never says when an agent should prefer this over other router configuration tools, nor when 'force' is appropriate versus dangerous, leaving the Network Guard decision unexplained.

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