unifi_gen_getradiusprofileoverviewpage

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no note on pagination behavior, default page size, result completeness, or what the 'generated from' API endpoint implies for output shape.

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 short, front-loaded sentence with no padding. The trailing 'generated from developer.ui.com/...' provenance is mildly useful for tracing the underlying API but is not behavioral information, keeping this 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?

With no output schema, zero-described parameters, and a duplicate sibling, the description is the only place an agent could learn what the tool returns or how to page/filter. It supplies none of that, so an agent cannot call it correctly without guessing.

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, offset, filter). While limit/offset are self-explanatory pagination names, the description says nothing about the filter string syntax or what fields it matches on — the parameter that most needs explanation is left entirely undocumented.

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 specific verb and resource ('List Radius Profiles'), so the basic operation is unambiguous. However, it does nothing to differentiate this tool from the near-identical sibling 'unifi_net_list_radius_profiles' in the same toolset, leaving the agent to guess which of the two to call.

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 versus the sibling list tool, no mention of pagination expectations, and no prerequisites or context. The only guidance is the implicit 'it lists radius profiles', which the name already conveys.

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