system_snmp_sysinfo_get

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states what data is retrieved, without mentioning permissions, side effects, or behavior when vdom parameter is used. For a read operation, this is minimally acceptable, but lacks important context like whether the tool requires special privileges or if it modifies state.

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, front-loaded sentence that precisely states the tool's action. Every word adds value, with no filler or repetition. It is appropriately sized for a simple read tool.

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 that the tool has an output schema (covering return values) and only one optional parameter, the description is nearly complete. It could be slightly enhanced by noting the read-only nature or scope, but for a low-complexity tool it is sufficient.

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 100% coverage with a full description for the vdom parameter. The tool description does not add any additional meaning beyond what the schema already provides. According to the rubric, baseline is 3 when coverage is high and description adds no extra value.

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 retrieves SNMP system info and enumerates specific fields (contact, location, description, trap thresholds). The verb 'Get' and resource 'SNMP system info' make the purpose unambiguous. It is well-differentiated from sibling tools like system_snmp_community_list or system_snmp_user_list.

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 the tool is for retrieving SNMP system info, but provides no explicit guidance on when to use it over alternatives or conditions where it should not be used. No context about prerequisites or limitations is given. The usage is implied but not explicitly directed.

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