fm_remove

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

With no annotations, the description must carry behavioral disclosure, and it only discloses that the operation may trash or delete depending on settings. It does not explain whether deletion is permanent, what confirm actually does, or what happens when confirm is false; the 'confirm: Required' statement also conflicts with the schema where confirm is not required.

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 with the primary behavior, and uses a clear Args block. Every sentence is relevant, though the 'confirm: Required' line is misleading given the schema.

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 destructive/mutating file operation with no annotations and minimal schema info, the description is under-specified. It omits important context such as confirmation behavior, path interpretation, error cases, and conditions under which delete replaces trash; output schema exists, so the return format is less of a gap.

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%, so the description must compensate, but it only repeats parameter names ('paths', 'confirm') with minimal meaning. It fails to describe path format/scope or the role of confirm beyond 'Required', which is contradicted by the schema default false.

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 states a specific action ('Move paths to trash') on paths and notes that deletion may occur depending on panel settings. It does not explicitly differentiate itself from sibling tools like fm_trash or fm_move, so it misses the top score.

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?

There is no guidance about when to use fm_remove rather than fm_trash, fm_move, or other file operations. The only usage-related instruction is 'confirm: Required', which is not a when-to-use or alternative-condition statement.

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