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. 'Delete a folder' conveys destructiveness but says nothing about whether deletion is permanent, recursive, or fails when the folder contains content, nor does it state any required permissions. This is a significant transparency gap 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 brief, but brevity is not appropriate sizing here: it omits critical context such as side effects, account scoping, and folder semantics. It reads as an under-specified one-liner rather than a well-structured definition.

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?

Although an output schema exists and the parameter count is small, the description is incomplete for a safe invocation of a destructive tool. It does not explain the role of account_id, the behavior on non-empty folders, reversibility, or any prerequisites, leaving the agent without essential 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?

Schema description coverage is 0%, so the description needed to compensate, but it says nothing about account_id or folder_id. The parameter names are reasonably self-explanatory, but the description adds no meaning beyond the schema's bare parameter names.

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 states a specific verb ('Delete') and resource ('folder'), making the core operation clear. It is distinguishable from sibling folder tools by the delete verb, though it does not explicitly differentiate itself from similar delete_* tools by scope or semantics.

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?

There is no guidance on when to use this tool versus alternatives like rename_folder or get_folder_details, nor any mention of prerequisites or context such as the folder existing or belonging to the given account. The description only states the action itself, so an agent must infer usage entirely from the tool name.

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