set_snmp

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'configure SNMP' without mentioning side effects, whether it enables/disables SNMP, or any impact on monitoring. This is insufficient for a mutating tool.

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 extremely short, almost terse. It lacks structured information and does not earn its place as a helpful specification; it is under-specified rather than concise.

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's simplicity, a short description could suffice, but without annotations, parameter explanations, or usage context, it is incomplete. The presence of an output schema does not compensate for the lack of behavioral and parameter information.

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 adds no meaning for the parameters 'enabled' and 'community'. It does not mention what these parameters control or how they relate to SNMP configuration, leaving the agent without any semantic guidance.

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 '配置 SNMP' means 'Configure SNMP', which identifies the resource and action but is vague. It does not specify what aspects are configured (e.g., enable/disable, community string), nor does it explicitly distinguish from sibling get_snmp_config.

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?

No guidance is provided on when to use this tool versus alternatives. The sibling get_snmp_config implies a get/set pair, but the description does not state any context or exclusions.

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