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. 'Watch files and directories for changes' implies ongoing monitoring, but the description doesn't reveal whether this creates persistent watchers, how events are delivered, whether this consumes system resources, or what happens when multiple watchers are created. For a monitoring tool with zero annotation coverage, this minimal description leaves critical behavioral aspects unspecified.

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 wasted words. It's appropriately sized for the tool's complexity and gets straight to the point without unnecessary elaboration. Every word earns its place in conveying the core functionality.

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 (monitoring functionality with 5 parameters), lack of annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, how events are structured, whether watchers persist across sessions, or how to interpret different action values. For a monitoring tool with behavioral implications, this minimal description leaves too many contextual questions unanswered.

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 5 parameters with their types, enums, defaults, and basic descriptions. The description adds no additional parameter semantics beyond what's in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 as 'Watch files and directories for changes' which includes a specific verb ('watch') and resources ('files and directories'). It distinguishes itself from siblings like 'list_directory', 'read_file', or 'get_file_metadata' which perform different operations. However, it doesn't explicitly differentiate from potential monitoring-related siblings beyond the basic verb+resource statement.

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. There's no mention of prerequisites, when this tool is appropriate versus other file operations, or what scenarios warrant file watching. Given the many sibling tools for file operations (list_directory, read_file, search_files, etc.), the lack of comparative guidance is a significant gap.

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