List local LAN DNS rules

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The parenthetical about gracefully warning on controller versions without LAN DNS adds genuine behavioral context beyond the annotations, but nothing else about pagination, empty results, or site scoping is disclosed.

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 sentence with the purpose front-loaded and zero filler. It is efficient, though the parenthetical is the only substantive detail and the whole thing borders on under-specified rather than merely concise.

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 read-only list tool with an output schema, the definition covers the core action and one version-compatibility caveat, which is roughly adequate. The unexplained site parameter and lack of any scoping or empty-result context leave clear gaps.

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?

The single parameter, site, has 0% schema description coverage, so the description carries the full burden and adds nothing — no explanation of whether site is required, what format it takes, or what happens when it is omitted. With one undocumented parameter and no compensating text, this falls below the baseline.

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 local LAN DNS records"), which clearly separates it from the other list_* siblings such as list_lan_networks or list_acls. It does not explicitly name an alternative or narrow the scope further, so it stops short of a 5.

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 mention of prerequisites, and no pointer to a related tool or alternative. The agent must infer that this is the tool for enumerating LAN DNS entries purely from the name and the word "List".

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