AI FileSystem MCP

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

With no annotations provided, the description carries full burden. It mentions atomicity and the rollback capability (implied by 'rollbackOnError' parameter), but doesn't disclose critical behavioral traits like: what happens on partial failures, transaction isolation characteristics, performance implications, or error handling details beyond rollback.

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?

Extremely concise single sentence that front-loads the core purpose. Every word earns its place with no redundancy or unnecessary elaboration.

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 transactional tool with 2 parameters (one being a complex array of operations), no annotations, and no output schema, the description is insufficient. It doesn't explain what constitutes a successful transaction, return values, error formats, or practical constraints for atomic file operations.

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 fully documents both parameters. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain operation ordering, atomicity guarantees for specific operation types, or constraints on operation combinations.

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 ('file operations') with the key characteristic 'in an atomic transaction'. It distinguishes from siblings like 'batch_operations' by specifying atomicity, but doesn't explicitly contrast with all file operation tools like 'update_file' or 'write_file'.

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 explicit guidance on when to use this tool versus alternatives like 'batch_operations' or individual file operation tools. The description implies atomic execution but doesn't specify scenarios where this is preferred over non-transactional approaches or prerequisites for use.

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