delete_path

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

The description lacks behavioral transparency beyond the basic action. There are no annotations, so the description must disclose side effects, permissions, or error conditions, but it does not. For a destructive tool, this is insufficient.

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 a single sentence, which is concise but overly brief. It sacrifices crucial information for brevity, making it minimally adequate.

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 destructive nature, lack of annotations, and two parameters, the description is severely incomplete. It does not mention return values, error handling, permissions, or the permanent nature of deletion.

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 description adds no semantic value to the parameters. The schema has 0% description coverage, and the description does not explain the 'path' or 'recursive' parameters (e.g., behavior when recursive is false, path requirements). This is 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 clearly states 'Delete a file or directory,' providing a specific verb and resource. It effectively distinguishes from sibling tools like copy_file or move_path, which perform different operations.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., when to use recursive, prerequisites, or that it might permanently delete without trash). No context is given for appropriate usage.

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