cycle_poe_port

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. 'Power cycle' implies a disruptive action, but the description does not state that PoE power to the attached device will drop, that the client will be temporarily disconnected, or whether the switch remains otherwise unaffected.

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?

This is a single, direct sentence with no filler, boilerplate, or repetition. It is appropriately sized for a simple two-parameter tool and front-loads the essential action and target.

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 simple two-parameter tool with complete schema coverage, this is minimally viable: an agent can select the tool and construct a call. However, because it is a disruptive operation, has no annotations, and has no output schema, adding a note about expected impact or return behavior would make it meaningfully more 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 input schema already documents both parameters at 100% coverage, so the description does not need to explain them. The description does not add any extra semantic detail beyond the schema, so the baseline score of 3 is appropriate.

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?

Fewer than ten words, the description names a specific verb ('Power cycle') and resource ('PoE port on a switch'), which clearly distinguishes it from sibling actions like rebooting a whole device (reboot_device) or reading network state (get_network_status). An agent can infer exactly what this tool does and what it operates on.

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 description gives no guidance about when to use this tool, when not to use it, or which sibling alternative might be more appropriate. With a large sibling list containing similar recovery-related actions like reboot_device and reconnect_client, the absence of any selection criteria is a real gap.

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