Get DNS policy

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 covered. The description adds nothing beyond that—no statement of what happens if the ID is unknown, whether the policy is scoped to a site, or any hint about response shape—so it contributes no behavioral context of its own.

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?

Five words with no wasted clauses, but this is under-specification rather than conciseness; the single sentence is front-loaded only in the sense that there is nothing else to be.

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 single-record lookup tool with no output schema and an undocumented required parameter needs the description to explain the ID and expected result. The description covers none of this, leaving the agent to infer how to call it correctly.

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?

There is a single parameter ('id') with 0% schema description coverage, so the description must carry the burden of explaining it. It never mentions the id at all—not that it is the policy identifier, not its format, not where to obtain one (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 fragment 'Detail for one DNS policy' identifies the resource and makes clear this returns a single policy rather than a list (distinguishing it from unifi_net_list_dns_policies). However, it largely restates the name/title 'Get DNS policy' and never says what 'detail' comprises or that a policy ID is required to fetch it.

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_list_dns_policies, unifi_raw_request, or the description-equivalent unifi_gen_getdnspolicy. No prerequisites or exclusions are stated; the agent must infer usage from the name alone.

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