Write a remote file (SFTP)

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

No annotations provided, so description carries full burden. Mentions UTF-8 text payload but lacks details on overwrite behavior, permission handling, error cases, and mode parameter. Incomplete for a write 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?

Short and front-loaded, but lacks essential information. One sentence plus a hint. Could be more structured by listing key parameters or constraints.

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?

Five parameters, no output schema, no annotations. Description is too brief to guide correct invocation. Missing required parameter details, return value, and error handling.

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 description adds no meaning to any parameter (mode, remotePath, content, mkdirParents, connectionName). The word 'payload' loosely relates to content but no explicit explanations.

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?

Clearly states action (write), resource (remote file), protocol (SFTP), and provides a specific use case (staging config files). Distinguishes from siblings like read_remote_file and upload_file.

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?

Suggests when to use (staging config files for later movement by exec) and implies an alternative workflow (exec for moving). Does not explicitly state when not to use or compare to upload_file, but provides useful context.

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