ssh_dir_delete

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

The description indicates the operation is recursive and returns a status dictionary, but lacks details on side effects, reversibility, or permission requirements. With no annotations, the description bears full responsibility and only partially fulfills it.

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 short and front-loaded with the main purpose. It is efficient, though slightly more structure (e.g., bullet points) could improve readability.

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 the existence of many sibling tools and the destructive nature of the operation, the description lacks completeness. It does not discuss error conditions, output schema details, or safety considerations, leaving gaps for an AI agent.

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?

The input schema covers all three parameters with descriptions (100% coverage), so the description adds no additional meaning. It does not mention path, dry_run, or use_sudo beyond what schema provides.

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 directory and its contents recursively. The verb 'delete' and resource 'directory' are explicit, and it distinguishes from sibling tools like ssh_dir_remove (likely for empty directories) and ssh_dir_batch_delete_files (for files).

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?

No guidance on when to use this tool versus alternatives is provided. There is no mention of prerequisites, warnings, or cases where it should not be used, which is a significant omission given the destructive nature of the operation.

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