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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely non-redundant behavior: the folder is destroyed but its contained QR codes survive and are re-parented to the company root. It omits permission requirements and whether the delete is reversible.

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?

Two short sentences, zero filler, with the primary action front-loaded and the consequential side effect immediately after. Every clause 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 single-parameter destructive delete with no output schema, the description covers the one thing an agent cannot infer: what happens to the folder's contents. Remaining gaps (auth scope, failure modes) are minor against annotations that already flag destructiveness.

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?

Only one parameter (a UUID 'id') exists and schema description coverage is 0%, so the description carries the burden but never mentions the identifier at all. The parameter is self-evident from its name and type, so this is a minor gap rather than a serious one.

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 ('Delete a folder') and adds the crucial scoping detail that QR codes inside are preserved and relocated to the company root, which effectively separates it from qrs_delete and folders_rename. It does not name a sibling explicitly, so it falls just short of the top band.

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 only implied: the side-effect note ('codes are kept and move back to the company root') tells an agent this is a safe non-cascading delete, which informs the decision. However there is no explicit when-to-use, when-not-to-use, or alternative (e.g. folders_rename for reorganizing) named.

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