delete_directory

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

With no annotations, the description carries the full burden. It discloses the directory-only constraint and the optional recursive behavior, but it does not explicitly state that deletion is permanent, irreversible, or that recursive=true is the default. For a destructive operation, more explicit caution would improve 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?

The English portion is concise and front-loaded, but the Chinese translation duplicates the English content without adding information. This redundancy means the description isn't as tight as it could be, though it remains short overall.

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 simple two-parameter tool, 100% schema coverage, and existence of an output schema, the description covers the essential use cases and constraints. It could mention the permanent nature of deletion or the default recursive behavior, but those are partially implied by the tool name and schema, so the description is fairly 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?

Schema description coverage is 100%, and the description does not add meaningful parameter-specific details beyond what the schema already provides. The phrase 'optionally all its contents' paraphrases the recursive parameter but adds no new semantics; the schema already explains defaults and behavior.

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's function: 'Delete a directory and optionally all its contents.' It specifies the resource (directory) and distinguishes it from file deletion by noting 'Only works on directories, not files.' The reference to the 'delete' tool for ambiguous paths further clarifies its scope relative to siblings.

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 provides explicit guidance: 'Only works on directories, not files' and 'Use ‘delete’ tool if you’re unsure whether the path is a file or directory.' This tells the agent exactly when to choose this tool over the generic delete tool, satisfying the need for usage context.

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