dhcp_networks

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

No annotations are provided, so the description carries the burden; it implies a read-only listing via 'List' and explains what the returned records mean (per-subnet options handed out on lease). However, it says nothing about permissions, pagination, or failure behavior, and the trailing note about booleans is opaque rather than informative.

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 verb and resource, and the field enumeration is efficient. The closing sentence 'No boolean fields here to normalize' is an internal note that adds little value to an agent and slightly dilutes the otherwise tight phrasing.

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-value detail is not required in the description; purpose, path, and record content are covered. The only real omission is any mention of the sole required parameter, which keeps it short of fully complete.

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?

There is one parameter (`device_name`) with 0% schema description coverage, and the description never mentions it. The gap is mitigated because the parameter name and title are self-explanatory and the tool is obviously device-scoped, but the description adds no semantics beyond the schema.

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 verb (List) and resource (DHCP server networks) with the exact API path `/ip/dhcp-server/network`, then enumerates the returned fields. It also distinguishes itself from the sibling `dhcp_servers` by describing these as the per-subnet options the server hands out, so an agent can separate the two without opening either schema.

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 by the resource description (per-subnet lease options) and the cross-reference to `dhcp_servers`, but there is no explicit when-to-use / when-not-to-use guidance or any stated prerequisites. Adequate but leaves routing to inference.

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