dhcp_static_mappings

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

The readOnlyHint annotation already declares this is a safe read, so the [READ] tag is largely redundant. The description does add the useful fact that it returns MAC↔IP pairings, but says nothing about pagination, empty results, or auth requirements beyond the annotation-covered safety profile.

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?

Front-loaded with a bracketed mode tag followed by the resource and a compact Args block. Every line earns its place with no filler, though the [READ] tag duplicates the annotation.

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 single-optional-parameter read tool with no output schema, there is little more an agent needs: it knows it is safe, what it returns conceptually, and how the one parameter behaves. Return-shape detail is the only minor omission.

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 coverage is 0% and the parameter has no description, so the description carries the burden here. It explains that "target" is a firewall target name from config and that omitting it selects the default, which is meaningful semantics the schema does not supply. Only the string format/valid values remain unspecified.

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?

"DHCP static (reserved) mappings (MAC ↔ IP)" states a concrete resource and even hints at the returned data shape, and "static (reserved)" implicitly distinguishes it from dynamic-lease tools. It doesn't explicitly name its closest sibling dhcp_leases, so it falls short of full sibling 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 [READ] marker signals it is a read operation, but there is no statement of when to use this rather than dhcp_leases or any other DHCP/status tool, and no prerequisites or exclusions are given. Usage must be inferred from the name alone.

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