ssh_db_import

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

No annotations are provided, so the description carries full burden for behavioral traits. It fails to disclose important behaviors such as potential data loss (the 'drop' parameter for MongoDB implies destructive action), required permissions, or error handling. The description merely states a generic import action.

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 very concise (one sentence) and front-loaded with the core purpose. However, it could be slightly expanded without losing conciseness to include key behavioral notes.

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 complexity (9 parameters, no output schema, no annotations), the description is too sparse. It does not explain the import process, return value, prerequisites (e.g., SSH connection established), or that the 'drop' parameter is MongoDB-specific. More context is needed for safe 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?

Schema coverage is 100%, so baseline is 3. The description does not add any extra meaning beyond the parameter descriptions in the schema. For example, it does not clarify the role of 'drop' or provide context for default values.

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?

Description clearly states the action (import), resource (database from SQL file), and supported database types (MySQL, PostgreSQL, MongoDB). It distinguishes from sibling tools like ssh_db_dump (export) and ssh_db_query (query) by specifying the import operation.

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 on when to use this tool versus alternatives such as ssh_db_dump for exports or ssh_db_query for queries. The description does not provide context about when not to use it or mention prerequisites like SSH connectivity.

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