delete_folder

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

With no annotations, the description carries the full burden. It does disclose that a non-existent folder yields a message, but omits critical destructive details such as whether deletion is recursive, permanent, or what the success return value is. This is insufficient for a destructive tool.

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 compact and front-loaded with the core action, using just two sentences. The second sentence covers an edge case without unnecessary words, making it highly efficient.

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 a simple single-parameter delete operation, but the description omits the success response and whether deletion applies to non-empty folders. Without an output schema or annotations, these gaps leave the agent uncertain about the tool's full behavior. The non-existence message is helpful but not sufficient for complete context.

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 single parameter 'folder' is described as 'given name', adding some meaning beyond the raw schema string type. However, it does not clarify if this is a path or a simple name, leaving ambiguity. Since there is no schema description, this partial compensation warrants a mid score.

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 it deletes a folder by name using the specific verb 'delete' and resource 'folder'. This inherently distinguishes it from sibling read/write/create tools.

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 on when to use this tool versus alternatives like bash or python_file for deletion. It implies usage for folder deletion but lacks exclusions or context for choosing it over other tools.

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