AI FileSystem MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Execute' which implies mutation, but fails to detail critical traits like whether operations are atomic, require specific permissions, have rate limits, or what happens on errors (though the schema hints at 'continueOnError'). This leaves significant gaps for a tool handling potentially destructive file operations.

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, efficient sentence with zero waste—it directly states the tool's function without unnecessary details. It's appropriately sized and front-loaded, making it easy to grasp quickly, though this conciseness comes at the cost of completeness in other dimensions.

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?

Given the tool's complexity (handling batch file operations with potential mutations), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on behavior, error handling, return values, and usage context, making it inadequate for safe and effective tool invocation by an AI agent.

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, but it only vaguely references 'multiple file operations' without explaining parameters like 'operations', 'dryRun', or 'continueOnError'. It adds minimal meaning beyond the schema, which itself defines parameters clearly but without descriptions. The baseline is lowered due to poor coverage, but the description doesn't adequately fill the gaps.

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 ('Execute') and resource ('multiple file operations') with the scope 'in batch', which is specific and actionable. However, it doesn't explicitly distinguish this tool from sibling tools like 'move_file' or 'transaction', which might also handle multiple operations, leaving room for improvement in sibling differentiation.

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 like 'move_file' for single operations or 'transaction' for grouped changes. It lacks context about prerequisites, such as needing file paths or permissions, and doesn't mention any exclusions or specific scenarios where batch processing is preferred.

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