list_dhcp_leases

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description contributes the shape of the returned data (the four lease attributes), which is useful, but adds nothing about pagination, lease counts, or how stale entries are handled.

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 noun phrase with a parenthetical field list; nothing is wasted and the core resource is stated first. It is a fragment rather than a full sentence, which keeps it terse but slightly limits readability for an agent scanning many tools.

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 zero-parameter, read-only listing tool with an output schema and read-only annotations, the description covers what is needed to call it correctly. The only meaningful gap is not explicitly contrasting it with the DHCP reservation siblings.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent parameters or filtering options that the schema does not support.

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 resource (current DHCP leases) and enumerates the returned fields (hostname, IP, MAC, seconds left), so the agent knows exactly what it gets. It does not explicitly distinguish itself from the sibling list_dhcp_reservations, leaving the lease-vs-reservation distinction to inference.

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' implies this is for inspecting active, dynamically assigned leases rather than configured reservations, which is usable implied guidance. However, there is no explicit when-to-use statement, no mention of when the sibling list_dhcp_reservations is the better choice, and no prerequisites noted.

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