Arping Host

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that ARP is layer-2/local-subnet only, that it typically requires elevated privileges or a local interface, that it produces no response across routers, or what the output looks like — all of which materially change whether an agent should call it.

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?

Four words, so there is no padding, but the brevity comes from under-specification rather than efficiency — nothing is front-loaded because nothing beyond the name is stated.

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 network diagnostic tool with no annotations and no output schema, the description should at minimum cover the local-subnet constraint, privilege needs, and expected result. None of that is present, so an agent has to guess whether the call is even valid in its environment.

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 100% (host and count are both documented inline), so the schema already does the parameter work. The description adds nothing about host format (IP vs hostname), whether count means per-second packets, or timeouts, so baseline 3 applies.

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 names a specific technique and resource (ARP ping a host), so the agent can tell roughly what it does. But it is essentially a restatement of the name/title and gives no basis for distinguishing it from the sibling ping_host, arp_table, or nmap_scan tools.

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 rather than ping_host (ICMP) or arp_table (read the ARP cache). The only usage signal is implied by the word 'ARP', which is not explained anywhere.

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