sassy_move

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

With no annotations, the description carries the full burden of disclosing behavior. It explicitly states that moves from/to protected paths are blocked and overwrites are refused unless a prior sassy_safe_delete is performed. These are critical safety traits for a mutating operation, beyond what the schema alone would convey.

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 extremely concise: two sentences, no fluff, with the main purpose front-loaded and safety constraints immediately following. Every word 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 two-parameter move tool, the description covers the core operation and the most important behavioral constraints. An output schema exists, so return values need not be explained. It is reasonably complete, though it omits minor details like error conditions or prerequisite checks beyond protected paths.

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. However, it does not explain the meaning of 'source' or 'destination' beyond their names and the general 'move or rename' concept. It does not add detail about path formats, whether destination can be a directory, or how rename vs. move is determined.

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 'Move or rename a file/directory,' which is a specific verb and resource. This distinguishes it from other sibling tools like sassy_copy, sassy_read_file, or sassy_write_file.

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 makes it clear that this tool is for moving or renaming, and it provides important usage constraints (blocks protected paths, refuses overwrite without explicit safe delete). It does not explicitly name alternatives, but the context is clear enough for an agent to infer when to use it.

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