deleteLanNetwork

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

The destructiveHint=true annotation already tells the agent the operation is destructive, and the description adds no further behavioral context — no cascading effects on attached devices or profiles, no irreversibility statement, no prerequisite conditions. The description is consistent with the annotation but contributes nothing beyond it.

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?

Single sentence with no filler: the verb, object, and lookup key are front-loaded and every word earns its place. This is appropriately sized for the information it conveys.

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 destructive two-parameter tool with 0% schema coverage and no output schema, the description is incomplete: an agent cannot tell what siteId is for, whether deletion cascades to devices, or what response to expect. A single sentence may suffice for a list tool, not for a mutation with an under-documented parameter set.

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 description coverage is 0%, so the description must compensate; it clarifies that networkId is the lookup key ('by its network ID') but leaves siteId entirely unexplained — its role, optionality, and relationship to networkId are ambiguous. A destructive call with two weakly documented parameters needs more.

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 combines a specific verb ('Delete'), a clear resource ('a LAN network'), and the identification method ('by its network ID'). Among siblings such as createLanNetwork, updateLanNetwork, and getLanNetworkList, the delete verb unambiguously identifies this tool's purpose.

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 is provided on when this tool should be used, what must hold before calling it (e.g., having obtained a networkId from getLanNetworkList), or which alternatives might be more appropriate. No exclusions or alternative routing is given.

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