Delete Folder

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add one useful behavioral detail: the tool returns a message when the folder does not exist. However, it does not disclose whether deletion is recursive, permanent, or restricted to empty folders, which are important 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 short and front-loaded with the primary action, followed by a relevant edge case. The phrase 'This function will' is mild filler, but both sentences contribute useful information and there is no unnecessary verbosity.

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?

The tool is simple with one parameter and no output schema, but as a destructive operation with no annotations, the description should clarify permanence, recursion behavior, and whether the folder must be empty. It covers the non-existent case but leaves these important details unresolved.

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 0%, so the description must compensate for the undocumented 'folder' parameter. It only refers to 'the given name,' which adds minimal meaning beyond the schema's type string. No details about path format, absolute vs relative, or naming constraints are provided.

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 specific operation: deleting a folder by name. It is unambiguous and naturally distinguishes itself from sibling tools like create_folder, read_file, and write_file, so an agent can identify the correct resource and action without additional context.

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?

No guidance is provided about when to use this tool versus alternatives such as bash, which could also delete folders. There is no mention of prerequisites, constraints, or scenarios where another tool would be more appropriate.

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