system_info

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

No annotations are present, so the description must disclose behavioral traits. It states the tool fetches information (a read operation) but does not confirm idempotence, safety, or lack of side effects. Given the SNMP context, it is likely a read-only fetch, but this is not explicitly stated. The description lacks clarity on response size or potential errors.

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, well-structured sentence that front-loads the main action and lists the returned OIDs. It is efficient, though it could be slightly improved by separating the list of OIDs or adding a note about parameter requirements.

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 simple tool with one parameter and no output schema, the description provides a complete list of retrieved OIDs, which is the core information needed. However, it lacks details about error conditions, response format, or whether the tool supports authentication options, which would be helpful for the agent.

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%, and the description does not add meaning to the 'host' parameter beyond the schema's type declaration. It does not explain formatting, examples, or constraints (e.g., IP vs hostname). The parameter remains ambiguous.

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 explicitly identifies the specific MIB group (SNMPv2-MIB::system) and lists the OIDs retrieved, making it clear what information the tool returns. The name 'system_info' is generic but the description adds precise context, and it is clearly distinct from sibling tools like interfaces_list or snmp_walk.

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 provides no guidance on when to use this tool versus alternatives such as snmp_get or snmp_walk. There is no mention of prerequisites, conditions, or exclusions, leaving the agent to infer the use case solely from the name and listed OIDs.

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