unifi_gen_getdnspolicypage

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. Beyond that the description adds only the upstream API path (v11.0.97/getdnspolicypage); it says nothing about pagination behavior for limit/offset, result ordering, or what a call returns.

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 and resource. The provenance clause is marginal filler but harmless; nothing bloats it.

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 paginated list tool with three undocumented parameters and no output schema, the description should explain pagination semantics and the filter parameter's format. It also omits how to distinguish this generated mirror from the native unifi_net_list_dns_policies.

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 three parameters (limit, offset, filter) have 0% schema description coverage, and the description provides no compensating detail. limit/offset are conventional enough to guess, but the filter syntax and accepted fields are completely opaque.

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 DNS Policies" names a specific verb and resource, so an agent can tell it enumerates DNS policies. However, it gives no hint on how this differs from the sibling unifi_net_list_dns_policies, and the "generated from..." suffix adds provenance rather than purpose.

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 prerequisites, and no mention of the nearly identical sibling unifi_net_list_dns_policies or unifi_gen_getdnspolicy for single-item retrieval. The agent must infer usage purely from the name.

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