ssh_sftp_upload

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

No annotations are provided, so the description carries the full burden. It fails to disclose behaviors such as whether files are overwritten, whether intermediate directories are created, or error handling for invalid sessions. The word 'Upload' implies mutation but lacks safety or side-effect details.

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 coherent sentence of 13 words, front-loading the action and context. Every word adds value; no redundancy.

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 no annotations or output schema, the description covers the essential purpose and prerequisite but is missing behavioral details (overwrite, permissions, error handling) that an agent might need. It is minimally viable for a simple upload tool.

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 schema already documents all parameters. The description adds context about 'reusing' the session and SFTP protocol, but does not provide additional semantic details beyond what the schema already conveys (e.g., local_path, remote_path, session_id). Baseline 3 is appropriate.

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 (upload), resource (local file to remote board over SFTP), and key context (reusing an existing SSH session). It distinguishes from sibling tools like ssh_sftp_download and ssh_shell_* operations.

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 implies when to use (for file upload over SFTP) and mentions the prerequisite of an existing SSH session. It does not explicitly list alternatives or exclusions, but the context is clear enough for an AI agent to infer usage.

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