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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds genuinely new behavior beyond that — the operation is non-recursive and cascades nothing ('nothing is deleted with it', a non-empty folder 'stays'). It does not say whether a non-empty or missing folder produces an error versus a silent no-op, which matters given idempotentHint=false.

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?

Short, front-loaded, and the safety-relevant precondition comes before the consent rule. 'And nothing is deleted with it' overlaps somewhat with 'a folder with docs or folders in it stays', so there is minor redundancy.

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 two-parameter destructive tool with full schema coverage and a rich annotation set, the description covers the essential unknowns: emptiness precondition, no cascading deletion, and user-consent requirement. Only the failure mode for a non-empty or nonexistent folder is left unstated.

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 100%, so both parameters are already documented; the description only restates the path format example that the schema already supplies and says nothing about the workspace parameter's defaulting behavior. Baseline 3 is appropriate since the schema carries the parameter burden.

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 ('Removes an empty folder') and immediately bounds the scope to empty folders, which clearly separates it from mkdir and from any content-deleting operation. An agent can identify the operation and its precondition 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?

'Only when the user asks' gives an explicit consent gate that rules out proactive cleanup, and the note that a folder containing docs or folders 'stays' tells the agent when the call will not succeed. It does not name an alternative (e.g. listing with tree/ls first to verify emptiness), so it stops just short of full when/when-not guidance.

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