snmp_table

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

Without annotations, the description carries the full burden. It discloses column-name mapping best-effort behavior and fallback to numeric OIDs, which is a key behavioral trait. However, it lacks details on permissions, rate limits, or idempotency.

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?

Two well-structured sentences. The first conveys the core purpose and output format, the second adds a caveat. No redundant information.

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?

Given the tool has no output schema and two simple parameters, the description explains the return structure and a key limitation (column mapping). It covers most needed context for invocation, though error behavior or SNMP version requirements are missing.

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?

With 0% schema description coverage, the description does not explain the 'host' or 'table_oid' parameters beyond their names. No additional meaning or constraints are provided, 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 action 'Walk and tabularize an SNMP table' and specifies the output format. It distinguishes from sibling tools like 'snmp_walk' which returns flat data, by focusing on tabular output.

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 usage for SNMP table data via 'tabularize an SNMP table', but does not explicitly state when to use this tool vs alternatives (e.g., snmp_get, snmp_walk). No exclusions are given.

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