sassy_safe_delete

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

With no annotations, the description carries the transparency burden. It discloses the key behavioral trait: items are moved to a _DELETE_ folder in the same parent directory rather than permanently deleted, explaining the safety mechanism. It does not mention permissions, edge cases, or undo behavior, but the core non-destructive behavior is clearly communicated.

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 two sentences, front-loaded with the primary action, then adding a concise rationale. Every sentence earns its place, with no unnecessary repetition or 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?

For a simple one-parameter tool, the description sufficiently explains the core purpose, the safety mechanism, and the staging location. It does not address potential edge cases (e.g., existing _DELETE_ folder), but given the existence of an output schema and the tool's simplicity, it is adequately complete.

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 coverage is 0% for the single 'path' parameter. The description only implies that path can be a file or directory, adding minimal semantic value. It does not explain path format, absoluteness, or any constraints, leaving the agent to infer from the parameter name alone.

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 tool's action: moving a file or directory to a _DELETE_ staging folder. This specific verb+resource distinguishes it from siblings like sassy_move or sassy_copy, emphasizing a safe-deletion workflow rather than generic file operations.

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?

Provides clear context that this is the safe alternative to permanent deletion, positioning it as the go-to for review-before-delete scenarios. However, it does not explicitly name alternative tools or state when not to use it, missing a small opportunity for stronger guidance.

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