ssh_dir_batch_delete_files

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

No annotations provided, so description carries full burden. It only states the action and return type, but omits crucial behaviors: whether deletion is recursive, permission requirements (sudo usage), and implications of the destructive operation. The use_sudo parameter is present but not explained.

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?

Very concise at two sentences, front-loaded with the action. However, it could include more contextual details without becoming verbose. Still well-structured and to the point.

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?

Despite having an output schema (mentioned in context signals), the description lacks essential context: whether deletion is recursive, error handling, and the importance of dry_run for safety. For a destructive batch operation, this is incomplete.

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 covers all 4 parameters with descriptions (100% coverage). The description adds no extra meaning beyond the schema's parameter descriptions. Baseline 3 is appropriate as no additional value is provided.

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 action: delete all files matching a pattern under a directory. It distinguishes from siblings like ssh_dir_delete (directory deletion) and ssh_file_* (single file operations), as this is the only batch pattern-deletion tool.

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 explicit guidance on when to use this tool vs alternatives like ssh_dir_list_files_basic for preview or ssh_file_delete for single files. The dry_run parameter exists but is not mentioned as a preview step. Lacks when-not-to-use or alternative references.

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