createLanNetwork

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

Annotations include destructiveHint=true, so the bar is lower, but the description adds no behavioral context beyond the action. It does not mention potential side effects such as network disruption, irreversibility, or any requirement for an existing site, and it neither contradicts nor elaborates on the destructive hint.

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 sentence that puts the action and resource first and lists key fields with no filler. Every word earns its place, and the structure is immediately scannable.

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 tool with 7 parameters, one required nested object, no output schema, and a destructiveHint, the description is under-specified. It does not mention what the tool returns, whether siteId is required for a valid call, or what side effects may occur, leaving an agent dependent entirely on the schema.

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 description highlights VLAN, gateway/subnet, and DHCP settings, giving a rough sense of the primary parameters. However, with 71% schema coverage, most fields are already described in the schema, and the description adds no new detail and omits purpose, igmpSnoopEnable, and siteId.

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 states a specific verb ('Create') and resource ('LAN network'), and lists the core configuration aspects (VLAN, gateway/subnet, DHCP settings). This clearly differentiates it from sibling tools like updateLanNetwork, deleteLanNetwork, and createLanProfile.

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 phrase 'Create a new LAN network' implies the tool is for creation, but there is no explicit guidance on when to use it versus alternatives like updateLanNetwork or deleteLanNetwork, and no prerequisites are mentioned. The intended use case is clear but not contrasted with related tools.

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