snmp_user_remove

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

With no annotations at all, the description carries the full burden and does reasonably well: it discloses that the operation is destructive (remove), that it is non-persistent until saved, that it is gated behind unlock, and that the underlying CLI is unverified. That last caveat is unusual and valuable. It does not describe failure behavior or what happens on an unknown name.

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?

Three short sentences, front-loaded with the action and followed by the operational caveats. Each sentence carries distinct information. The 'Gate this in the hub with unlock' fragment is terse to the point of being slightly cryptic, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and for a single-parameter mutation the description covers the important gaps: non-persistence, the unlock prerequisite, and a reliability caveat. What remains missing is what happens when the named user is absent, which is minor at this complexity.

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?

There is one required parameter, 'name', with 0% schema description coverage, so the description must compensate. It only implicitly indicates that name identifies the allow-listed SNMP user; there is no guidance on accepted format, case sensitivity, or whether the user must already exist.

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?

States a specific verb and resource: 'Remove an allow-listed SNMP user (noAuthUser)'. The parenthetical pins down exactly which kind of user, which separates it from the community/view siblings. It stops short of naming a specific alternative, but the resource is unambiguous.

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?

'Gate this in the hub with unlock' and 'Does not save' together imply the workflow (unlock, then save) without explicitly saying so or mentioning save_config by name. There is no explicit when-not guidance against the sibling removal tools, leaving the agent to infer the choice from the resource noun.

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