nexterm_import_ssh_config

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

Annotations already declare it as a non-read-only, non-idempotent, open-world mutation, so safety basics are covered. The description adds little beyond that: it does not disclose duplicate handling, partial-failure behavior, permission requirements, or whether imports overwrite or append, which matter for a non-idempotent batch operation.

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 single sentence is front-loaded and free of filler. It is appropriately concise, though its brevity comes at the cost of useful operational detail.

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 nested input schema, 0% schema description coverage, no output schema, and non-idempotent batch mutation semantics, the description is not complete enough. An agent would still be unsure about duplicate handling, failure modes, and the meaning of nested server fields.

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 there are two top-level parameters plus nested server fields. The description implies "servers" is a batch and "folder_id" selects a target folder, but it does not explain server fields such as identity_ids, jump_host_ids, port defaults, or keyboard_layout, nor how a null folder_id behaves.

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 states a specific verb ("Import") and resource ("a typed batch of SSH server definitions") plus a destination ("into a Nexterm folder"). It is clearly distinct from single-entry creation siblings like nexterm_create_entry, though it does not explicitly name alternatives.

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 batch import versus creating entries individually, nor any prerequisites, conflict behavior, or when-not conditions. The only usage signal is implied by the tool name and the word "Import."

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