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

Annotations only supply destructiveHint=true, so the description carries real added weight: it discloses that subfolders are deleted recursively while contained files survive by moving to the library root, plus permanence. It omits permission requirements and whether confirmation/recovery is possible, keeping it short of a 5.

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 tight sentences: the destructive action is front-loaded, the cascade consequence follows, and the API mapping is a useful trailing detail. No filler.

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?

With no output schema and a single well-documented parameter, the description covers the essential semantics of a destructive recursive operation. Missing auth/permission notes and any indication of failure modes prevent a 5.

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?

There is a single parameter ('folder') with 100% schema description coverage ('Folder UUID.'), so the schema already does the work. The description adds no format or identification detail beyond the schema, making the baseline 3 correct.

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?

States a specific verb and resource ('Permanently delete a folder') and distinguishes itself from the many sibling delete_* tools by naming the exact object type. The cascade semantics make the scope unambiguous.

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?

Usage is implied rather than stated: the word 'Permanently' signals irreversibility, but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as update_folder, move_files_to_folder, or get_folder. An agent must infer that this is the terminal removal path.

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