List LAN and VLAN networks

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful provenance — results are a merge of two configuration sources — but the sentence is cut off mid-path, leaving it unclear exactly what is combined or whether conflicting entries are reconciled. No mention of pagination or auth needs.

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?

It is short and front-loads the verb, which is good, but the trailing ellipsis means the only substantive detail is truncated rather than concise. The space saved is not earned because the omitted content is what an agent would need.

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 described, and annotations cover the safety semantics. However, the truncated source-merge explanation and the undocumentated `site` parameter leave real gaps for what is otherwise a simple one-parameter read tool.

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 single `site` parameter has 0% schema description coverage, so the description was the only place to explain it, and it says nothing about whether site is required, what format it takes, or what happens when it is omitted (global vs per-site listing). With one undocumented parameter the minimum-viable bar is not met.

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?

"List configured LAN/VLAN networks" states a specific verb and resource, and the merge note (setting/lan/networks and /interface...) tells the agent this is a combined view rather than a single endpoint. It doesn't differentiate itself from siblings like list_wlans or list_networks-equivalents, but the resource is unambiguous.

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?

No guidance on when to reach for this versus other list_* tools; the agent has to infer that LAN/VLAN networks are distinct from WLANs or network services. There are also no prerequisites or notes on when the merged view is preferable to per-source calls.

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