List Ipv6 Neighbors

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

The readOnlyHint annotation already tells the agent this is a safe read, so the description carries a reduced burden. Beyond that, it adds nothing: no indication of what the neighbor table contains, whether results are cached/live, or any filtering or pagination behavior.

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?

A single, front-loaded sentence with zero filler — appropriate for a trivial list tool. It is arguably under-specified rather than over-long, but nothing in it is wasted.

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?

An output schema exists, so return-value shape need not be described. For a no-argument list tool that is close to sufficient, but the description omits the one thing that would help an agent choose it confidently: what the IPv6 neighbor table actually represents here (NDP cache vs. static entries) relative to the similar IPv6 listing siblings.

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 tool takes zero parameters, so the baseline is 4. There is no parameter detail the description could meaningfully add or omit, and the empty schema is self-explanatory for a parameterless list operation.

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?

States a specific verb ('列出'/list) and resource (IPv6 邻居/neighbors), which is a recognizable distinct concept from the sibling 'list_ipv6_static_bindings'. It does not, however, explicitly distinguish itself from adjacent IPv6 siblings such as get_ipv6_config or get_ipv6_line_detail.

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?

No guidance on when to use this versus the many other IPv6/neighbor-adjacent tools in the sibling list. There are no prerequisites, no scope notes (e.g., which interface or table), and no exclusions, leaving the agent to infer usage entirely.

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