arp

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

No annotations are provided, so the description carries full burden for behavioral traits. It only states 'Show ARP/NDP table' without disclosing whether it is read-only, requires privileges, or covers both IPv4 and IPv6. Minimal transparency beyond the basic function.

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?

The description is a single concise sentence with no unnecessary words. It is front-loaded and efficiently conveys the core action. However, it may be too brief for a tool without annotations or output schema, slightly reducing completeness.

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 simple display command with three optional filters, the description is adequate but lacks details on output format, behavior when no filters are applied, or relation to NDP. Given the server has 17 sibling tools, more context could help the AI agent choose 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?

The input schema covers 100% of parameters with descriptions (mac, ip, search). The tool description adds no additional parameter semantics. Since schema description coverage is high, the baseline is 3; no extra value is provided.

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 'Show ARP/NDP table' clearly indicates the tool displays the ARP or NDP table. It uses a specific verb ('Show') and resource ('ARP/NDP table'), distinguishing it from siblings like 'dhcp' or 'dns' which show different tables. However, it does not explicitly differentiate itself from similar 'show' commands.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. Users must rely solely on the tool name and schema to infer usage context.

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