Network interfaces

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: the data comes from `ip -j address` and the IP address field is left empty when that binary is unavailable, signalling graceful degradation. It says nothing about performance, privilege requirements or result ordering.

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 sentence with no filler, and the concrete field list comes first. It is under-specified rather than verbose, and the opening 'Each interface with...' reads as a dangling fragment rather than a statement of what the tool does.

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?

With zero parameters, a full output schema and complete annotations, the burden on the description is low, so what is there is mostly adequate. The gap is the missing action statement and any hint of when to prefer this over listening_ports or system_overview.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's mention of `ip -j address` is incidental context, not parameter semantics.

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 the resource (network interfaces) and enumerates the specific fields returned (state, MTU, MAC, byte/error/drop counters, IP addresses), which is enough for an agent to know this is the NIC-inventory tool rather than listening_ports or system_overview. However, it is a noun-phrase fragment with no verb, so the 'list/read' framing has to be inferred.

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 when-to-use guidance and no mention of the closest sibling, listening_ports, which also deals with network data and could plausibly be confused with per-interface detail. An agent must infer selection purely from the resource name.

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