monitor_network_io

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is fully covered. The description adds 'per interface' scoping, which is useful but does not disclose details like sampling period, units, or whether rates are instantaneous or averaged.

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, focused phrase with no filler. Every word contributes to the core meaning, and it is immediately readable.

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-only monitoring tool, the description sufficiently tells an agent what to expect: network I/O rates broken down by interface. It does not specify the output format or units, but the simplicity of the tool reduces the need for extensive detail.

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 has zero parameters, so there is no semantic burden on the description. The empty input schema fully specifies the invocation, and the baseline of 4 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 clearly identifies the resource (network I/O) and the specific scope (per interface), which differentiates it from sibling monitors like monitor_cpu and monitor_disk_io. It lacks an explicit verb, but the tool name 'monitor_network_io' combined with the description makes the purpose unambiguous.

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 implies when to use the tool: whenever per-interface network I/O rates are needed. However, it does not explicitly state exclusions or mention alternatives, such as speed_test or get_vnstat_data, so the guidance is inferred rather than explicit.

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