unifi_gen_getdnspolicy

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds nothing beyond a documentation URL — no note on error behavior for an unknown ID, response shape, or any context beyond what annotations supply.

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?

It is a single short line with no padding, but it is also almost entirely content-free apart from the source-URL provenance. Brevity here comes from under-specification rather than disciplined writing.

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 lookup tool with an undocumented parameter and a duplicate-named sibling, the description does not equip the agent to choose or invoke it correctly. The 'generated from' URL is provenance, not usable operational context.

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%, and the description does not mention dnsPolicyId at all. The agent must infer from the name and UUID format that it is the policy identifier; nothing is said about where to obtain it (e.g., from unifi_net_list_dns_policies).

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 states a verb and resource ('Get DNS Policy'), so the basic action is identifiable. But it offers no scope detail and does not distinguish this tool from the near-identical sibling unifi_net_get_dns_policy, leaving the agent to guess which 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 guidance on when to use this versus unifi_net_get_dns_policy or unifi_net_list_dns_policies. Usage is only inferable from the tool name and the single required ID parameter.

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