Cross-Platform Filesystem MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'move or rename' implies mutation/destructive action, it doesn't specify whether the operation is atomic, reversible, requires specific permissions, affects linked references, or has rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 perfectly concise - a single sentence with zero wasted words that immediately communicates the core functionality. It's front-loaded with the essential information and earns its place efficiently.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address important contextual aspects: what happens on success/failure, whether the operation overwrites existing files, how to handle cross-device moves, or what the return value contains. The agent lacks critical information for proper tool invocation.

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 100%, so the schema already documents both parameters ('source path' and 'destination path'). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain path formats, relative vs absolute paths, or rename semantics when source and destination differ only in name. Baseline 3 is appropriate when schema does the heavy lifting.

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 purpose with specific verbs ('move or rename') and resources ('file or directory'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'copy_item' (which copies rather than moves) or 'rename' functionality that might be implied in other 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'move_item' over 'copy_item' (for moving vs copying), when renaming might be preferable to moving, or any prerequisites like needing appropriate permissions. The agent must infer usage from the name alone.

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