ssh_move

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

The description only says 'Move or rename' without disclosing behavioral details such as whether it overwrites existing files, if it preserves permissions, or if it is an atomic operation. With no annotations, more transparency is needed.

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 succinct with a main sentence followed by a bulleted parameter list. It is well-structured and easy to scan, but could include more details without becoming verbose.

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 simple move operation, the description covers the basic parameters but omits context like return values, error handling, and whether it follows symlinks. With no output schema, these details would help the agent fully understand the tool's behavior.

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?

The description adds basic explanations for each parameter (source: current path, dest: new path, host: SSH host alias from config, uses default if omitted). Given 0% schema coverage, this compensates somewhat but lacks specifics on path format or constraints.

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 clearly states the action ('Move or rename') and resource ('file/directory on the remote server'), making the tool's purpose immediately understandable. It distinguishes from siblings like ssh_delete and ssh_upload by specifying the move/rename 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?

The description provides no guidance on when to use this tool versus its siblings, such as ssh_cp or ssh_delete. No mention of alternatives or best practices for file relocation.

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