unifi_gen_adoptdevice

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

The annotations already declare destructive=true, openWorld=true, idempotent=false and readOnly=false, so the safety risk is visible. The description adds nothing: it does not say the adoption is irreversible, does not list rate limits or the need for device-limit bypass (ignoreDeviceLimit), and does not explain what the preview returns when confirm is omitted.

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 very short and has a clear lead-in, so it is not verbose. However, one of its two clauses is only a documentation-source pointer, which does not help an agent decide whether or how to call the tool.

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?

This is a destructive mutation with no output schema and no information about prerequisites or post-conditions. A complete definition would cover what 'adopt' does to the device record, the pending-device requirement, and the preview behavior; instead, it defers entirely to an external docs URL.

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 100%, so the schema already explains body, confirm and dry_run clearly. The description adds no parameter meaning, which is acceptable given full coverage, so the baseline of 3 applies.

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 phrase 'Adopt Devices' gives a clear verb and resource, which is more than many generated stubs. However, it does not distinguish this tool from the sibling unifi_net_adopt_devices, which appears to do the same job, nor does it identify what state a device must be in (e.g., pending) before adoption.

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 contains no guidance about when to use this tool instead of unifi_net_adopt_devices or unifi_net_device_action, and no mention of the prerequisites involved in adopting a device. The only usage hints (the confirm field 'YES' and dry_run preview) appear in the schema, not the description.

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