cleanup

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool deletes temporary unpack directories and explains the two deletion modes, but it does not warn about irreversibility, whether deletion is recursive, or the potential risk of `all=true` deleting more than intended.

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 short, front-loaded, and contains no filler. Every sentence adds meaningful information about what is deleted and how the two parameters control behavior.

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?

Given that this is a destructive action with no annotations, the description covers the core behavior and parameter semantics but omitsuseful context such as when to use it after unpack/repack, what the output schema reports, and whether deletion is permanent. An output schema exists, so return values need not be described in detail, but usage context and safety caveats would improve completeness.

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 does: `dir_path` is explained as a single directory, and `all=true` means delete all unpack directories by prefix in temp. This adds meaningful semantics beyond the bare schema properties, though it could clarify the exact prefix matching rules.

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 clearly states the verb 'Удалить' (delete) and the resource 'временный каталог unpack' (temporary unpack directory), and it distinguishes the two modes: deleting a single directory vs. deleting all unpack directories via `all=true`. It is easy for an agent to understand what the tool does, though it does not explicitly contrast it with sibling tools.

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?

The description gives per-parameter usage guidance: `dir_path` targets one directory, and `all=true` targets all unpack directories by prefix. However, it does not state when cleanup should be invoked relative to unpack/repack operations, nor does it mention any conditions or alternatives.

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