unifi_gen_getwansoverviewpage

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, but the description adds nothing beyond them. It does not mention pagination behavior, page-size limits, what a 'page' contains, or any ordering of results.

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, front-loaded sentence with no filler. The trailing generated-from URL is of marginal use to an agent but takes little space and is not harmful.

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?

A paginated list tool with no output schema, 0% parameter documentation, and no explanation of result shape or pagination semantics is under-described. The agent could call it, but cannot predict how to page through results or what the response contains.

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%, so both limit and offset are bare integers in the schema with no description anywhere. The description does not compensate: it never mentions pagination, the maximum page size of 200, or what offset indexes into.

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 WAN Interfaces" gives a specific verb and resource, so the agent knows exactly what is returned at a high level. It does not distinguish this from the near-identical sibling unifi_net_list_wans, leaving the agent to guess which of the two 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 statement of when to use this tool, when not to, or which alternative to prefer. The presence of both this tool and unifi_net_list_wans makes the missing routing guidance a real cost, not a minor omission.

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