AI FileSystem MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'semantic understanding' but doesn't explain what that entails (e.g., AI-based meaning matching vs. keyword search), nor does it cover aspects like performance, error handling, or output format. This leaves significant gaps for a tool with 5 parameters.

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 no wasted words. It's front-loaded with the core purpose ('Search files') and includes a key qualifier ('using semantic understanding'), making it easy to parse quickly.

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 (5 parameters, no annotations, no output schema), the description is insufficient. It lacks details on behavior, output format, and differentiation from siblings, making it incomplete for effective agent use. The high parameter count and absence of structured support heighten the need for more descriptive context.

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 all 5 parameters. The description adds no parameter-specific information beyond the tool's general purpose, which is adequate but not additive. This meets the baseline for high schema coverage.

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 'Search files using semantic understanding' clearly states the verb ('search') and resource ('files'), and the 'semantic understanding' qualifier distinguishes it from basic text search. However, it doesn't explicitly differentiate from sibling tools like 'fuzzy_search', 'search_content', or 'search_files', which limits its score.

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. With multiple sibling search tools (e.g., 'fuzzy_search', 'search_content', 'search_files'), there's no indication of what makes 'semantic_search' unique or when it's preferred, leaving the agent without usage context.

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