upload

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states that it uploads a file and returns a dictionary, but omits critical traits such as whether the remote file is overwritten, whether directories are created, authentication requirements, or error handling. This is insufficient for a mutation 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 concise and well-structured with clear Args and Returns sections. Every sentence earns its place, though the parameter descriptions could be more substantive. Overall, it is appropriately sized and front-loaded.

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 is simple but the description omits essential context such as the requirement of an active session (prerequisite from connect), potential side effects, and error behavior. With no annotations and no output schema, the description is incomplete for an AI agent to use reliably.

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 Args section lists all three parameters but the descriptions are tautological (e.g., 'local_path: Local file path'), adding little meaning beyond the parameter names. Since the schema has 0% description coverage, the tool description should compensate but does not provide any additional detail about formats, constraints, or behavior.

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 tool's action and resource: 'Upload file to SSH server'. This is a specific verb+resource construction that unambiguously distinguishes it from siblings like download and execute.

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. It does not mention that a session must be active (via connect) or that download is the counterpart for retrieval. The purpose is implied but no explicit usage context is given.

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