Delete Folder

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

Discloses required confirm flag, default behavior (only empty folder), cascade effect (like rm -r), and that documents are soft-deleted (recoverable). No annotations present; description carries full burden.

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?

Three sentences, no redundancy. Front-loaded with 'Delete a folder' then immediate conditions.

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?

Covers behavior, safety, alternatives, and recovery. No output schema, but description explains 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?

Schema has 100% coverage but description adds context: path is POSIX, confirm as safety guard, cascade for non-empty. Incorporates real-world analogy (rm -r).

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?

Clear verb 'delete' with specific resource 'folder'. Distinguishes from siblings by mentioning move_folder/move_markdown as alternatives for reorganization.

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?

Explicitly states when to use (delete folder) and when not (reorganizing, prefer move tools). Provides conditions for cascade and confirm flags.

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