ssh_session_upload_content

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

With no annotations, the description only mentions 'Upload content directly... no local temp files'. It does not disclose overwrite behavior, permissions, error handling, or other side effects, leaving significant gaps 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 short and front-loaded with the core action; the Args list is slightly redundant with the schema but adds value. Could be more compact, but no wasted sentences.

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 simplicity of an upload tool and presence of an output schema, the description covers the basic mechanism but lacks prerequisites (active session), failure modes, and usage context. Adequate for a straightforward tool but not comprehensive.

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 description coverage is 0%, but the description's Args section adds essential meaning: 'Base64-encoded content', 'Destination path on the remote host', and encoding options, far exceeding the schema's bare type/title.

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 verb 'Upload' and resource 'content to a remote host via SSH', with a notable distinction 'no local temp files' that sets it apart from siblings like 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 on when to use this tool versus alternatives like ssh_session_download_content or reverse_shell_upload_content; lacks explicit when-not-to-use or prerequisite context.

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