unifi_gen_executeadopteddeviceaction

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true; the description adds nothing about what gets disrupted, that a device will be restarted, or what the confirm/dry_run safety flow means in practice. The only content beyond the name is a documentation URL, so no behavioral context is contributed.

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?

It is short, but the brevity comes from under-specification rather than efficiency: one name-restating line plus a provenance URL, with no front-loaded explanation of the operation.

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 tool with four parameters and no output schema, the description provides nothing an agent needs in order to call it safely or correctly.

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% and the schema itself explains 'confirm' and 'dry_run'; the description only points to a vendor docs page for the body schema. It adds no meaning about the body's RESTART-only constraint or expected deviceId semantics.

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 title ('Execute Adopted Device Action') and adds only a generator URL. It never says what the action is (the schema reveals it is a RESTART) nor how it differs from near-duplicate siblings such as unifi_net_device_action, unifi_net_reboot_device, unifi_gen_executeportaction, or unifi_gen_executeconnectedclientaction.

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, when-not-to-use, or alternative routing is given. An agent has to infer from the name alone whether this or the many other device-action siblings should be called.

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