upload

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

Annotations are completely absent, so the description carries the full burden of behavioral disclosure. It only states the basic action and does not mention whether an existing remote file is overwritten, whether directories are created, what permissions are required, or any side effects. This is a significant gap for a mutation-like upload operation.

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 single sentence is concise and front-loaded with the core action ('Upload file'), containing no filler. It effectively states the purpose in minimal words, though it could be slightly expanded with useful context without losing conciseness.

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 tool with no annotations and no output schema, the description is too sparse. It does not explain what happens on success or failure, whether the remote path refers to a file or directory, or how the 'connected server' is determined. The schema covers parameter names but the overall operational context is incomplete.

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 input schema already provides descriptions for all three parameters, with 100% coverage, so the baseline applies. The description adds no additional parameter meaning, but because the schema fully covers 'localPath', 'remotePath', and 'connectionName', a score of 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 file') and the target ('connected server'), which distinguishes it from siblings like 'download' or 'execute-command'. However, it does not explicitly differentiate from these siblings by naming them or elaborating on the remote context, so it misses the top score of 5.

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 gives no guidance on when to use this tool versus alternatives like 'download' or 'execute-command'. It does not mention prerequisites, such as needing an existing server connection, nor when not to use this tool. Usage is only vaguely implied by the verb 'Upload'.

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