interface_traffic

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

No annotations, so the description carries the burden and does well: it discloses validation behavior (shape-only, existence not checked, RouterOS errors surface as-is), the once=yes prompt-return semantics, and the empty-dict case. Missing only auth/permission or rate-limit context.

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?

Front-loaded purpose, then two tight paragraphs on interface validation and return shape. Parenthetical command example is useful; slight redundancy across sentences but no wasted fluff.

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?

An output schema exists so return values needn't be explained, yet the description still clarifies the typical fields and empty-dict edge case. Combined with validation and timing semantics, the agent has enough to call correctly; only auth context is absent.

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 coverage is 0% and both properties lack descriptions, so the description must compensate. It explains `interface` validation semantics and the device_name requirement is implicit; no param format details (e.g., name syntax) are given, keeping it above baseline but not full.

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?

Specific verb+resource+scope: 'Current rx/tx traffic rate of one interface', with a concrete RouterOS command and explicit instant-reading semantics. Distinguishable from siblings like interface_monitor and torch by the 'one interface / single instantaneous reading' framing.

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?

No explicit when-to-use vs alternatives. It hints at scope (one interface, single reading) which implicitly contrasts with torch or interface_monitor, but never names an alternative or states exclusions, so the agent must infer routing.

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