ssh_dir_copy

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

The description only notes the action and return type (dictionary). With no annotations, it fails to disclose potential side effects (e.g., overwriting, permission requirements, or consequences of using sudo).

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 short (2 lines) and front-loaded with the core action. It is concise without being too brief, though some additional context would improve usability.

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?

The tool has 6 parameters (2 required) and a simple purpose. The description is minimal but covers the basic action and return type. For a tool with many siblings, more detail on when to use it would enhance completeness.

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?

All parameters are fully described in the input schema (100% coverage), so the description adds no additional context. A baseline score of 3 is appropriate given high schema coverage.

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 'Copy a directory recursively,' which is a specific verb and resource. It distinguishes from sibling tools like ssh_file_copy (file copy) and ssh_dir_transfer (possibly similar) by specifying recursion, but could be more explicit about what makes it unique.

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 is provided on when to use this tool versus alternatives (e.g., ssh_dir_transfer or ssh_file_copy). There are no conditions, prerequisites, or exclusions mentioned.

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