Prepare remote file operation

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

The description says 'Preview,' which strongly implies a non-destructive dry-run, yet annotations declare destructiveHint=true. This is a direct contradiction. The description adds no further context about the nature of the operation, such as whether changes are staged or require confirmation.

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 a single, front-loaded sentence that conveys the core purpose without extraneous words. It is highly concise and well-structured.

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 4-parameter tool with no output schema and minimal annotations, the description is too terse. It does not explain the workflow (prepare vs. execute), parameter dependencies, what 'configured remote roots' means, or how to safely use a destructive operation. Users would need external knowledge to invoke it correctly.

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%. The description lists the operation types (mkdir, copy, move, delete) but does not explain the roles of source, destination, or recursive, nor their interdependencies (e.g., destination needed for copy/move). It fails to compensate for the missing schema documentation.

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 'Preview' and the resource 'mkdir, copy, move, or delete inside configured remote roots.' It distinguishes the tool from siblings like write_file or transfer_files by indicating it is a preview/preparation step.

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 implies usage for previewing file operations before execution, providing clear context. However, it does not explicitly mention when to use this tool over alternatives (e.g., write_file for content, transfer_files for bulk), nor does it state that confirm_action may be needed to execute the prepared operation.

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