target_upload_file

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. 'Upload' implies a write operation, but the description does not mention side effects, permissions, connection requirements, or what happens on failure. This leaves important behavioral traits undisclosed.

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 extremely short, but this is under-specification rather than conciseness. A single sentence that omits nearly all useful information does not earn its place.

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 file upload operation with four parameters, no annotations, no output schema, and no behavioral details, the description is severely incomplete. It does not explain the data flow, prerequisites, or expected results.

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 schema has four parameters with zero description coverage, so the description must compensate. It does not mention a single parameter, leaving session_id, remote_path, content, and session_type entirely unexplained. This fails to add value beyond the bare schema.

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 names the operation ('Upload') and a vague resource ('target session'), making the basic purpose evident. However, 'target session' is ambiguous and the description does not differentiate this from sibling upload tools like ssh_session_upload_content or reverse_shell_upload_content.

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 given on when to use this tool versus alternatives such as target_download_file or any of the session-specific upload tools. The description implies a file transfer action but provides no context or exclusions.

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