list_ipv6_neighbors

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context that filters are non-destructive matching operations by specifying substring vs exact semantics, but discloses nothing about result volume, pagination, or whether an empty result differs from an unreachable device.

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?

Two sentences: the purpose first, then a compact Notes block that carries only non-obvious filter semantics. Every clause earns its place with no repetition of schema field names.

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 values need not be described, and the annotations cover safety. The remaining gap is the unexplained 'device' parameter and the absence of any hint about valid status values, but for a read-only list tool this is largely complete.

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%, so the description must carry the load, and it does for 4 of 5 parameters by defining substring matching for address_filter/mac_filter and exact matching for interface_filter/status_filter. The 'device' parameter remains entirely undocumented, and no example status values are given, which keeps it short of a 5.

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+resource ('Lists detailed IPv6 neighbor-discovery entries'), which is clearly distinct from siblings like list_ipv6_addresses and list_arp_entries in the namespace. However, it does not explicitly name or contrast with those related listing tools, so the differentiation relies on the reader's inference.

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 when-to-use guidance, no mention of alternatives (e.g., list_arp_entries or list_ipv6_addresses), and no stated prerequisites for reaching neighbor-discovery data. The notes cover filter behavior but say nothing about choosing this tool over its siblings.

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