interfaces

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

With no annotations, the description carries the full disclosure burden. It does imply a non-mutating enumeration and tells the agent what data categories come back, which is real value, but it says nothing about privileges needed, whether interfaces are discovered locally vs remotely, or whether results include down interfaces by default. Not contradictory, just thin.

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 the verb first and the returned fields packed into one efficient clause. No filler, no restatement of the tool name.

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 no-argument read tool with an output schema already documenting return values, this is nearly complete. The only gap worth naming is whether down interfaces are included and what scope of host is inspected, both of which would affect interpretation of results.

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?

Zero parameters with 100% schema coverage, so the baseline of 4 applies. The description adds no parameter information because there is none to add.

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?

Opens with a specific verb and resource ('List network interfaces') and enumerates exactly what is reported: up/down state, IPv4/IPv6 addresses, MAC, speed and error counters. The parenthetical 'physical and data link layers' hints at how it differs from the IP-focused sibling ip_config, but the differentiation is left implicit rather than stated.

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?

Usage is only implied by the enumeration of link-layer fields; there is no explicit 'use this when...' and no sibling is named, even though ip_config, arp_table and wifi_signal all overlap in the network-diagnostics space. An agent can infer this is the interface-inventory call, but must reason it out.

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