fast-filesystem-mcp

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. 'Performs batch operations' implies mutation capabilities, but it doesn't describe error handling, performance characteristics, permissions required, or what happens when operations fail. The description is minimal and lacks critical behavioral context for a tool that can delete, move, and overwrite files.

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 at just 5 words, front-loaded with the core purpose. There's zero wasted language or redundancy. Every word earns its place in communicating the essential function.

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 complex batch operation tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't address critical context like error behavior, atomicity of operations, performance implications, or what the tool returns. The minimal description leaves too many questions unanswered for safe and effective use.

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 all parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting, though the description could have explained the relationship between operation types and parameter requirements.

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 performs batch operations on multiple files, specifying the verb 'performs' and resource 'files' with the scope 'batch operations'. It distinguishes from single-file siblings like fast_copy_file and fast_delete_file by emphasizing batch processing, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for individual file operations (fast_copy_file, fast_delete_file, fast_move_file), the description doesn't indicate when batch processing is preferable or when to use single-operation tools instead.

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