delete_directory

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

No annotations are provided, so the description must fully disclose behavior. It explains that recursive deletion removes contents, but omits critical safety details such as irreversibility, permission requirements, and behavior when the directory is non-empty and recursive=False. This is a significant gap for a destructive operation.

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 concise and front-loaded with the primary purpose, followed by a clear and necessary Args section. Every sentence provides value, and there is no redundancy or wasted words.

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 deletion tool, it covers the core action and parameters, but lacks essential edge-case behavior such as failure modes for non-empty directories without recursive, reversibility, or permission errors. Given the presence of an output schema, return values need not be described, but behavioral completeness is only adequate.

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 schema's properties have no descriptions (0% schema coverage), but the description compensates by explaining that path is a relative path and recursive controls deletion of contents. This adds meaningful semantics beyond the bare schema types and defaults.

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 'Delete a directory on WD MyCloud' clearly identifies the operation (delete) and resource (directory), distinguishing it from sibling tool delete_file. The recursive parameter adds clarity about deletion scope.

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?

The description implies usage for deleting directories but does not explicitly mention when to prefer it over alternatives like delete_file, nor does it state prerequisites or exclusions. The recursive argument provides some context but no explicit 'when to use vs. not to use' guidance.

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