ssh_db_import

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Import database', implying a write operation, but fails to mention side effects like dropping existing data (though a drop parameter exists), authentication requirements, or that the import is performed over SSH. The description is too sparse to inform the agent about critical behaviors.

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 is very concise and to the point. However, it could be better structured by including more context without sacrificing conciseness. It earns its place but is minimal.

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 has 9 parameters (4 required) and no output schema or annotations, the description is far from complete. It does not explain the workflow, prerequisites (e.g., SSH access), or expected results, leaving significant gaps for effective agent usage.

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?

Since the input schema has 100% description coverage, the baseline is 3. The description does not add any additional meaning beyond the schema's parameter descriptions, so it meets the baseline but does not improve it.

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 'Import database from SQL file (MySQL, PostgreSQL, MongoDB)' clearly states the tool's action and supported database types, distinguishing it from sibling tools like ssh_db_dump (export) and ssh_db_query (query). However, it does not explicitly mention the SSH context or differentiate from alternatives like ssh_db_restore, so clarity is good but not perfect.

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 provides no guidance on when to use this tool versus alternatives such as ssh_db_dump (export) or ssh_db_query (query). There is no mention of prerequisites or context for selection, leaving the agent with insufficient direction.

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