delete_directory

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It mentions the recursive requirement but does not disclose that deletion is likely irreversible, whether permissions are required, what happens if recursive is false on a non-empty directory, or any side effects. The word 'Delete' gives some signal, but a destructive tool needs more transparency.

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 short sentences with no redundant information. The core action and the key parameter behavior are front-loaded, making it easy to scan.

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?

For a simple two-parameter tool, the description plus schema covers the basic invocation. However, because this is a destructive operation with no annotations and no output schema, a sentence about permanence, error behavior, or safety would have made it meaningfully more complete.

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 already documents both parameters fully (100% coverage). The description adds value by giving a concrete rule for when to set recursive=true, which goes slightly beyond the schema's static description. Path remains self-explanatory.

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 states a specific verb ('Delete') and resource ('directory'), which clearly separates it from sibling tools like delete_file, create_directory, and copy_file. An agent can tell immediately what operation is being exposed.

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?

It gives a clear usage hint for the recursive parameter ('Set recursive=true for non-empty'), which helps the agent decide how to invoke it. However, it does not explicitly state when to prefer this tool over alternatives such as delete_file, nor does it mention edge cases like failing on non-empty directories.

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