Get device details

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The only behavioral content the description adds is the word "adopted," which mildly scopes results but says nothing about error behavior for unknown/offline devices or what fields are returned.

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?

One short, front-loaded sentence with no filler. It is appropriately sized in form, though the brevity comes at the cost of substance rather than from efficient compression.

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 simple one-parameter read tool with full safety annotations and no output schema, the definition is minimally viable but leaves the key unknown: the identity format of deviceId and the shape of the returned detail. Annotations carry the safety burden, so the gap is narrow but real.

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 0% and the single parameter deviceId has no description in either the schema or the description text. The agent is not told whether deviceId is an internal ID, MAC address, or hostname, which matters for a lookup tool that will fail on a malformed identifier.

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?

"Detail for a single adopted device" names the resource (device) and scope (single, adopted) but uses a noun fragment rather than a verb, and never distinguishes itself from close siblings such as unifi_net_list_devices, unifi_gen_getadopteddevicedetails, or unifi_sm_get_host. An agent can guess it is a per-device read, but not which of several per-device reads to pick.

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 on when to use this vs. unifi_net_list_devices (many devices), unifi_net_list_pending_devices (unadopted), or unifi_net_get_device_stats (statistics). The only implicit constraint is "adopted," and no prerequisites or alternatives are stated.

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