List pending devices

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=true, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact — it is console-level and needs no siteId — but says nothing about result size, whether unadopted devices from all sites appear, or pagination behavior.

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 front-loaded sentence with zero filler; the scope qualifier immediately follows the resource. It is appropriately sized, though leaning toward under-specification rather than optimal density.

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 paginated list tool with no output schema and three undocumented parameters, the definition leaves the agent without guidance on filtering syntax, page size caps, or result shape. The console-level note helps routing but does not complete the picture.

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% for three parameters (limit, filter, offset), and the description does not mention any of them. It neither explains what 'filter' accepts nor that limit/offset imply pagination, so the agent must guess at formats — a real gap the description should have filled.

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?

States a specific resource — devices waiting to be adopted — and disambiguates it from the adopted-device siblings (unifi_net_list_devices / unifi_gen_listdevices) via the 'waiting to be adopted' qualifier. The verb 'list' is only implied by the name/title, but the scope is unambiguous.

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?

'console-level, no siteId required' gives real invocation context, but there is no explicit guidance on when to use this versus list_devices or the natural follow-up adopt_devices. The agent must infer that these are pre-adoption candidates and that unifi_net_adopt_devices is the next step.

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