delete_directory

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

Discloses safety features, allowed path restriction, and recursive confirmation requirement. Does not mention potential error conditions (e.g., deleting non-empty directory without recursive), permissions, or side effects beyond deletion.

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?

Three concise sentences, each providing distinct value. Front-loaded with purpose and safety, followed by key usage instructions. No redundant or unnecessary content.

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 absence of output schema, the description adequately explains the tool's core behavior and safety features. However, it omits what the return value indicates (e.g., success feedback) and does not cover edge cases like invalid paths or permission errors.

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?

Input schema covers all 4 parameters with descriptions (100% coverage), so baseline is 3. The description adds limited extra meaning, e.g., 'Use preview=true to see what will be deleted first' adds context but does not significantly deepen understanding 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?

Clearly specifies the verb 'delete' and resource 'directory'. Distinguishes from sibling 'delete_file' by focusing on directories, and adds safety context like 'protection checks' and 'allowed paths'.

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?

Provides clear guidance on when to use preview and require recursive confirmation. However, it does not explicitly state when to use this tool versus alternatives like 'delete_file' or 'list_directory' for assessment.

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