dhcp_leases

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about behavior: no statement that it is a read-only snapshot, whether results are live or cached, what happens on a router with no leases, or any permission requirement. Only the word 'Current' hints at data freshness.

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 fragment with zero filler, front-loaded on the resource being fetched. It is appropriately short for a no-argument read tool, though the parenthetical duplicates what the output schema already declares.

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 with zero parameters there is little surface area to cover. However, for a query tool with no annotations at all, the description should say that this is a safe read of live lease data and how it relates to the reservations tooling.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The parenthetical field list is descriptive of output rather than input, which is harmless but does not add parameter meaning.

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?

Names a specific resource (DHCP leases) and enumerates the fields returned (hostname, IP, MAC, lease time), which makes the retrieval target unambiguous. It lacks an explicit verb and does not name the sibling it differs from (list_reservations, get_dhcp_settings), so it stops short of full differentiation.

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 word 'Current' faintly implies active leases rather than static reservations, but there is no explicit when-to-use statement, no mention of list_reservations or get_dhcp_settings as alternatives, and no prerequisites. An agent must infer routing from sibling names alone.

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