Identify network devices that may be IoT but are not on the dedicated IoT VLAN. Use this to find devices missing isolation and improve network security.
Identify potential IoT devices that are not on the IoT VLAN
| Name | Required | Description | Default |
|---|---|---|---|
| iotVlanId | No | Optional IoT VLAN ID to exclude |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description needs to disclose whether detection is passive or active, whether it has side effects, and what it returns. It states only the high-level outcome, leaving the tool's operational behavior opaque.
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?
The description is a single, front-loaded sentence with no filler. It is compact and readable, though it trades detail for brevity.
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 one-optional-parameter read-style tool, the description gives the core purpose but omits the output/return behavior and any assumptions (e.g., requiring admin privileges or a scan). It is adequate for basic invocation but not 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?
The single parameter iotVlanId is fully described in the schema ('Optional IoT VLAN ID to exclude'), and the description adds no parameter-level detail. With 100% schema coverage, the baseline 3 applies.
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 names a specific action ('Identify') and a specific resource ('potential IoT devices that are not on the IoT VLAN'), which makes the tool's function clear. It does not explicitly compare itself to overlapping siblings like list_devices or search_network, so it falls short of full 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?
No guidance is given about when to choose this over alternatives such as list_devices or search_network, nor are any prerequisites or follow-up actions mentioned. The only contextual clue is the tool's name, so an agent must infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.