unifi_gen_listhosts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds nothing beyond restating the name and a source URL – no note on default page size, pagination termination, or what a "host" represents in the site-manager model.

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?

A single short sentence with the verb and resource front-loaded, so there is no bloat. The trailing "generated from developer.ui.com/..." clause is provenance metadata of marginal use to a calling agent, keeping it just short of a 5.

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?

The tool is simple and annotations are rich, but the description leaves open what a host is, what the response contains, and how it differs from unifi_sm_list_hosts. For a list tool in a catalog with heavily duplicated host/site/device listing tools, that disambiguation is the minimum needed.

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%, with both pageSize and nextToken self-documented as pagination controls, so the baseline of 3 applies. The description contributes no additional meaning about default values or how nextToken chains across calls.

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 verb and resource ("List Hosts") and adds API provenance, which is better than a bare tautology. However, it does not distinguish this tool from the near-identical sibling unifi_sm_list_hosts, nor does it relate to unifi_gen_gethostbyid, leaving the agent unable to tell which host-listing tool 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 versus unifi_sm_list_hosts or the many unifi_net_* list tools. The only extra signal is the upstream endpoint path, which tells a developer where it came from but not when an agent should call it.

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