ssh_deploy

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

With no annotations, the description fully discloses mutation, default backup behavior, options for owner/permissions/sudo/restart, automatic default detection, hooks, and security restrictions. This provides comprehensive transparency.

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 a single paragraph with six sentences, each adding distinct value: main action, state mutation, backup, options, defaults, hooks, restrictions. No unnecessary words.

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?

The description covers all major aspects: upload method, backup, options, defaults, hooks, security. However, it omits error handling behavior (e.g., what happens if a move fails) and does not describe the return value, leaving minor gaps.

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%, so baseline is 3. The description adds context by explaining the temporary-upload-then-move process and automatic default detection, enriching understanding of parameters like owner and permissions.

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 tool deploys local files to remote paths using a two-step upload-then-move process. It distinguishes from siblings like ssh_upload by specifying the temporary location and backup behavior.

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 implies usage via the detailed process but does not explicitly compare to alternatives such as ssh_upload or ssh_backup_create. An explicit 'use this when' statement would improve clarity.

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