ssh_deploy

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

No annotations provided, so description carries full burden. It discloses mutation of remote state, backup default, ability to disable backup, setting owner/permissions, sudo password, service restart, and hook execution. The blocking condition on readonly/restricted servers adds 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?

Single paragraph covers key points efficiently. Could be slightly more structured (e.g., bullet points), but it's concise and front-loaded with the primary action.

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 complexity, no output schema, and full parameter coverage, the description covers nearly all aspects: process, backup, permissions, sudo, restart, hooks, and blocking conditions. It is complete for an agent to decide and use correctly.

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 clear descriptions. The description adds context (e.g., temporary upload, default backup, detection of defaults) beyond schema, enhancing parameter understanding.

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 process (upload to temp then move). This differs from siblings like ssh_upload (simple upload) and ssh_sync (syncing), providing distinct purpose.

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?

Explicitly describes when to use: for deploying files with backup, permissions, sudo, hooks, and service restart. Also states it's blocked on readonly/restricted servers, guiding when not to use. No alternative tool named, but the detail implies appropriate usage.

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