unifi_gen_executeportaction

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotent behavior, so the safety profile is known. The description adds nothing beyond that: it never says that POWER_CYCLE disrupts a live port, never mentions the confirm/dry_run safety pattern, and never explains what happens on execution. It is a name plus a URL, contributing no behavioral context.

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 short and front-loads the action name, so it is not bloated. However, half of its content is a provenance URL ('generated from developer.ui.com/...') rather than information that helps an agent decide or invoke, so its brevity reflects missing content rather than efficiency.

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, non-idempotent mutation with five parameters, two undocumented required fields, and no output schema, the description should carry substantial weight. Instead it offers only a vendor doc link, leaving the agent unable to determine effect scope, prerequisites, or return behavior from the definition itself.

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 only 60%: body, confirm, and dry_run are documented in the schema, but the two required parameters portIdx and deviceId have no descriptions beyond min/max and a UUID pattern. The description does not compensate at all — it says nothing about port index numbering or how to obtain a deviceId.

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 restates the tool name ('Execute Port Action') and appends a documentation URL, which is effectively tautological. It never explains what a 'port action' does in this API (the schema hints at POWER_CYCLE only inside the body const), and it does not distinguish itself from the sibling unifi_net_port_action, which appears to offer overlapping capability.

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?

There is no guidance at all about when to use this tool, when not to, or how it relates to alternatives such as unifi_net_port_action, unifi_net_device_action, or unifi_gen_executeadopteddeviceaction. The presence of a near-identical sibling makes this absence costly, though the text is not actively misleading.

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