snmpwalk_scan

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

With no annotations present, the description must carry the full burden. It discloses that the target must be in tengu.toml allowed_hosts and that SNMP v3 needs extra auth parameters, which is helpful. However, it does not explicitly state that the operation is read-only or describe error/timeout behavior, leaving a notable gap.

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 well-organized with Args, Returns, and Notes sections, and the introductory SNMP context earns its place. It is slightly verbose but every sentence contributes meaningful information, making it efficient without being terse.

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 tool with 5 parameters, no annotations, and an output schema, the description covers purpose, parameter semantics, return value summary, and critical operational notes. The only missing piece is explicit guidance on when to select this tool against sibling scanning tools.

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 description coverage is 0%, but the description fully compensates by explaining every parameter's meaning, default, and acceptable values (e.g., community default 'public', version '1', '2c', or '3', oid default '.'). This provides semantic value well beyond the raw schema.

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 opens with 'Enumerate SNMP information from a network device using snmpwalk,' which clearly names the verb, resource, and tool. It further explains SNMP's typical use cases (device config, interfaces, routing tables), distinguishing it from sibling network scanners like nmap_scan or masscan_scan.

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 SNMP protocol explanation implies when this tool is useful (e.g., accessing device configuration), but there is no explicit statement about when to choose it over other scanning tools or when not to use it. Alternatives are not mentioned.

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