Write a file to the remote server

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

No annotations so description must carry full burden. States it writes via SFTP, but lacks details on overwrite behavior, error handling, or permission requirements. Adequate for basic understanding but not comprehensive.

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?

Two concise sentences, front-loaded with the core action, no redundant information. Every word adds value.

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?

With 7 parameters, 5 required, and no output schema or annotations, the description could include more about return behavior, overwrite safety, or prerequisites. Still, it covers the primary purpose.

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% with all parameters described. Description adds no extra parameter information beyond the schema, so baseline score 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?

Clearly states the action (writes text content via SFTP), the resource (file path on remote server), and distinguishes from sibling deploy_* tools by specifying use cases like config files and scripts.

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?

Provides explicit context when to use (config files, env files, scripts) and hints at alternatives (deploy_* recipes). Missing guidance on when not to use relative to exec or other tools, but sufficient for most agents.

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