Execute device action

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

Annotations already declare destructive=true, idempotent=false and openWorld=true, so the safety profile is covered structurally. The description adds only the underlying endpoint name and the casing mapping; it says nothing about the disruption a restart causes, how the confirm/preview gate behaves in practice, or error conditions.

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?

Three short, front-loaded sentences with no padding. However the brevity reflects under-specification rather than efficiency — the space saved is used on endpoint trivia instead of the action vocabulary.

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, open-world mutation with no output schema, an agent needs to know the valid action set, what the preview path returns, and what state changes result. None of that is present, and the overlap with unifi_net_reboot_device is unresolved.

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 75%, so most parameters are documented structurally. The description usefully notes that lowercase "restart" is mapped to the vendor value RESTART, which the schema's bare e.g. "RESTART" does not make explicit. deviceId and the confirm/dry_run semantics are left entirely to the schema.

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?

"Generic device action" restates the tool name rather than describing what it does; the only concrete content is that the vendor value is RESTART. It never states whether other action values exist, nor distinguishes itself from the sibling unifi_net_reboot_device, which appears to do an overlapping job.

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 when-to-use or when-not-to-use guidance. The obvious alternative, unifi_net_reboot_device (and unifi_gen_executeadopteddeviceaction / unifi_net_port_action), is never mentioned, so an agent has no basis for choosing between them.

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