delete_path

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral traits: destructive and irreversible, and specifies what can be deleted. It does not cover edge cases like permissions or failure on non-empty dirs without recursive, but the primary risk is clearly stated.

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 exactly two sentences, front-loaded with the action and the destructive warning. Every sentence earns its place, with no unnecessary fluff.

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 tool's simplicity and the presence of an output schema, the description covers the essential behavior and warning. It could explicitly mention that non-empty directories require recursive=true, but that is implied by 'empty directory'. Overall, it is complete enough for correct invocation.

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?

Since schema description coverage is 0%, the description must compensate. It explains the effect of recursive=true, but missing_ok is completely unaddressed. The meaning of missing_ok (whether to error when the path is absent) is left undocumented in both schema and description, leaving a significant gap.

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 starts with a specific verb 'Delete' and resource 'file, empty directory, or directory tree', clearly distinguishing it from siblings like copy_path and move_path. The recursive condition is also clarified, making the purpose unmistakable.

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 explicitly states when recursive=true is needed for directory trees and warns that the operation is 'DESTRUCTIVE and irreversible outside backups'. This gives clear contextual guidance, though it does not mention alternatives like move_path for non-destructive deletion.

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