ssh_upload

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

No annotations are provided. The description lacks details about authentication requirements, whether overwriting occurs, error handling, transfer protocol (e.g., SFTP/SCP), or recursion support. This is insufficient behavioral disclosure for a file transfer tool.

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 concise sentence. It could be slightly longer to include critical behavioral notes, but the current length is not wasteful. Efficient but not optimally informative.

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 lack of annotations and output schema, and the presence of sibling tools like ssh_download, the description should clarify aspects like authentication, protocol, and overwrite behavior. It fails to complete the picture for an agent to use it correctly.

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 the parameter descriptions (server, localPath, remotePath) are already present. The tool description does not add any extra meaning or usage context beyond what is in the schema, so baseline 3 applies.

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 'Upload file to remote SSH server' uses a specific verb and resource, clearly distinguishing it from siblings like ssh_download or ssh_sync. It directly states the action and target.

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 like ssh_sync or ssh_deploy. No mention of prerequisites (e.g., SSH key setup) or exclusions. Minimal context for appropriate use.

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