ssh_delete

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

Discloses auto-detection of path type, the two SFTP operations used, and the intentional lack of recursive support. Also notes password insecurity via plaintext transmission. No annotations, so description carries full burden.

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 efficient sentences: first states core function, second adds critical exclusion. No wasted 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?

Covers purpose, usage, behavior, and parameter context adequately for a delete tool. Lacks mention of return values or error handling, but acceptable given operational simplicity.

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% and parameters are well-described there. The description adds only context about 'absolute path' and SFTP protocol, not new parameter-level meaning beyond schema.

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 deletes a file or empty directory via SFTP, auto-detects path type, and distinguishes from recursive deletion using unlink/rmdir. This is specific and differentiates from sibling tools like ssh_exec.

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 states when to use (delete file/empty dir) and when not to use (recursive directory delete), with a clear alternative: use ssh_exec with rm -rf.

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