unifi_gen_getconnectedclientoverviewpage

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 about pagination behavior, total-count fields, default page size, or result ordering — all relevant for a paged listing endpoint. The provenance URL is metadata, not 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 line, front-loaded with the action. The trailing "generated from developer.ui.com/..." is provenance noise that doesn't help invocation, but it costs little.

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?

No output schema, no parameter documentation, and a terse label — for a paginated list endpoint with a free-form filter string, this leaves large gaps. The description should say what the page returns and how filter/limit/offset work together.

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?

Three parameters (limit, filter, offset) have 0% schema description coverage, so the description carries the full burden — yet it mentions none of them. The agent gets no idea of filter syntax, whether filter is a query string or JSON, or that limit is capped at 200.

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?

"List Connected Clients" gives a verb and resource, so the basic intent is clear. But it never distinguishes itself from the very similar siblings unifi_net_list_clients and unifi_gen_getconnectedclientdetails, and the description doesn't explain what an "overview page" contains versus those alternatives.

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 indication of when to use this tool rather than unifi_net_list_clients or unifi_gen_getconnectedclientdetails, despite both being present in the sibling list. The only additional text is a source-URL provenance note, which gives the agent no routing guidance.

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