unifi_gen_listdevices

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world behavior, so the safety profile is covered. The description contributes only a source URL and says nothing about result scope (site vs host), pagination behavior, or what a caller should expect back.

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 short and front-loaded, so it does not waste words, but it is under-specified rather than genuinely concise. Brevity here reflects minimal content rather than disciplined editing.

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 device-listing tool with four optional parameters and no output schema, the description does not clarify the namespace (site-manager vs network application) or the pagination model. In a toolset with multiple near-identical list-device siblings, this leaves a critical routing gap.

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?

All four parameters (time, pageSize, hostIds[], nextToken) are fully documented in the schema at 100% coverage, including the RFC3339 format and pagination token. The description adds no additional parameter semantics, so the baseline of 3 applies when the schema does all the work.

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 gives a clear verb-resource pair ("List Devices"), but it is essentially a restatement of the tool name, and 'generated from ...listdevices' only signals provenance. With three sibling list-device tools in scope (unifi_net_list_devices, unifi_sm_list_devices, unifi_gen_listdevices), it provides no differentiation.

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 when-to-use guidance, no mention of prerequisites, and no indication of how this differs from other device-listing or host-scoped siblings. The agent is left to infer everything from the name.

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