Sm Advanced Operations

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

With no annotations, the description carries the full burden, and it discloses almost nothing: it does not say that add_authorized_key mutates a security-sensitive SSH authorized_keys file, that install_* actions modify the host toolchain, whether actions are idempotent, where artifacts land, or what is returned. Naming "SSH" is a faint signal of sensitivity but no concrete behavioral context.

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?

A single short sentence is maximally concise, but it is under-specified rather than efficient — it spends its only sentence on a vague label instead of front-loading the action families or the SSH mutation risk.

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 5-parameter, 7-action, no-annotation, no-output-schema tool spanning Python/Node environment setup and SSH key installation, the description is far too thin. The agent is left to infer action-to-parameter mapping, side effects, and return behavior entirely from the schema.

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 100%, so every parameter is documented in the schema and the baseline is 3. However, the description adds nothing about which parameters apply to which action (path for venv vs package for install_package vs public_key for add_authorized_key), a gap the schema also leaves open.

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 offers only "Operations for SSH and specialized managers", which is a vague category rather than a specific verb+resource. It also under-represents the tool: SSH key handling is 1 of 7 actions, while the bulk (install_uv, create_venv, install_package, install_nvm, install_node, use_node) is Python venv and Node version setup, none of which the description hints at. An agent must open the schema's action enum to learn what this tool actually does.

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?

There is no guidance on when to use this tool versus siblings like sm_system_operations, sm_user_operations, or sm_service_operations, and no stated prerequisites (e.g. whether venv creation should precede install_package, or whether SSH key work requires elevated access). Nothing indicates exclusions or ordering.

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