Pcloud Delete Folder

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

With no annotations, the description must disclose destructive behavior and it does state deletion and that recursive removes contents. However, it stops short of noting irreversibility, permission requirements, or how a non-empty folder behaves when recursive is false, which are useful 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?

One short, front-loaded sentence states the action and the key modifier. There is no filler or duplicated information, so every word earns its place.

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?

For a simple two-parameter tool with an output schema, the basic delete-and-recursive behavior is present. The main gap is that it never says what happens when recursive is false and the folder is non-empty, a key runtime detail affecting successful invocation. Still adequate as a minimal viable description.

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. It adds meaning only for recursive ('remove its contents too'), while path is left to schema/context. This is a partial compensation for two parameters, not a complete semantic explanation.

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 begins with an explicit action and resource: 'Delete a folder in pCloud.' The noun 'folder' cleanly separates it from sibling tools like pcloud_delete_file and pcloud_list_folder, so an agent can tell which tool to pick without opening the schema.

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?

It clearly frames the tool's use as folder deletion and adds practical guidance with 'Set recursive to remove its contents too.' It does not explicitly contrast with the array of siblings or state a when-not condition, but the folder-vs-file distinction and recursive hint give enough context.

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