list_dhcp_leases

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

Annotations declare readOnlyHint=true, so the read-only nature is known. The description adds the context that it returns current assignments, which is slightly useful. It does not disclose pagination, sorting, or any additional behavioral traits, but the output schema likely covers return structure.

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?

The description is a single, front-loaded sentence that conveys the core function. There is minor redundancy with 'list' appearing as both verb and noun (列出...列表), but it is still compact and easy to parse.

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 simple read-only list tool with one optional parameter and an output schema, the description is largely sufficient. It would benefit from explicitly mentioning the ip_type parameter or noting that it only returns dynamic leases, but the schema and the parenthetical cover the essential context.

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 input schema has 100% description coverage for the single optional parameter ip_type, which is fully described as "v4" or "v6". The tool description adds no parameter-specific meaning, but since the schema already documents the parameter clearly, the baseline of 3 applies.

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 clearly states the tool lists DHCP leases (currently assigned IPs), using a specific verb and resource. The parenthetical 'currently assigned IP' distinguishes it from related tools like list_dhcp_static_bindings, making sibling differentiation clear.

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?

Usage is implied: if you need to see current DHCP leases, use this tool. However, there is no explicit when-to-use vs alternatives, no exclusions, and no guidance on when not to use it. The description states what it does but not how it fits among siblings.

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