ssh_delete

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

No annotations exist, so the description carries full burden. It discloses key behaviors: auto-detection of path type, unsupported recursive delete, and the underlying SFTP ops used. However, it does not mention what happens when trying to delete a non-empty directory or what the return value looks like.

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 sentences, no wasted words. First sentence defines purpose and behavior, second sentence states limitation and alternative. Information is front-loaded.

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?

No output schema, so return values are not explained. The description covers core behavior, limitations, and alternatives well. Lacks details on error handling and authentication flow, but these are partially covered by the input schema.

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 each parameter has a description. The description adds contextual value for the 'path' parameter by noting auto-detection but does not elaborate on other parameters beyond the 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 that the tool deletes a file or empty directory on a remote host via SFTP, specifying the specific resources (files/symlinks and empty dirs) and action. It also differentiates itself from sibling tool ssh_exec by noting that recursive delete is intentionally unsupported.

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 tells when to use (delete files/empty dirs) and when not to (recursive delete). Provides a clear alternative: use ssh_exec with `rm -rf` for recursive deletion, with rationale about traceability.

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