batchSetSwitchPortPoe

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

The destructiveHint annotation already signals that this changes device state. The description adds the scope of the operation (multiple ports) and the PoE mode semantics, but does not disclose consequences such as power loss to connected devices or any prerequisites. With annotations present, this is acceptable but not expansive.

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. Every phrase earns its place: the action, the object, the scope, and the mode semantics.

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 batch mutation of switch ports, the description covers the core intent and required poeMode values, but leaves the roles of switchMac, portList, and siteId to be inferred from names or schema. Without an output schema, the response behavior is also undisclosed, making the description adequate but incomplete.

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 coverage is only 25%, with most parameters undocumented. The description repeats the poeMode mapping already present in the schema and adds no new meaning for switchMac, portList, or siteId. Given the low coverage, the description should compensate but does not.

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 clearly identifies the action: batch enable/disable PoE on multiple switch ports, with an explicit on/off mapping. It also distinguishes itself from the singular sibling setSwitchPortPoe through the 'Batch' and 'multiple' qualifiers.

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 word 'Batch' plus 'multiple switch ports' clearly signals when this tool is appropriate, and the key sibling setSwitchPortPoe would be for single-port changes. It does not explicitly name the alternative or provide a when-not-to-use condition, so it stops just short of a 5.

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