interfaces_list

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

With no annotations, the description effectively communicates behavioral traits: merging of ifTable and ifXTable, handling of high-capacity counters, and automatic ifSpeed fallback. It fails to disclose if the tool has side effects or requires specific permissions, but for a read-only list operation, this is adequate.

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 concise and well-structured, starting with the core purpose and then adding technical details. No redundant information is present, and every sentence adds value.

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?

While the description covers the tool's operation and key behaviors, it lacks information about the output format (since no output schema is provided) and does not explain the 'host' parameter. For a simple one-parameter tool, these gaps are noticeable but not critical.

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 input schema has 0% description coverage and the single 'host' parameter has no explanation. The description does not clarify whether 'host' expects an IP address, hostname, or includes SNMP community details, leaving the agent to infer from context.

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 states the tool lists network interfaces via IF-MIB (RFC 2863), providing a specific verb and resource. It also explains the merging of tables, which distinguishes it from sibling tools like snmp_table or snmp_walk that may not have this specific logic.

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 does not mention when to use this tool versus alternatives. There is no guidance on prerequisites, such as SNMP credentials, or situations where other tools like snmp_get or device_detect might be more appropriate.

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