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 for behavioral disclosure. 'Execute shell commands' implies mutation/execution capability, but the description doesn't disclose critical behaviors: what 'multi-level security' entails (sandboxing? permission restrictions?), whether commands run locally or remotely, what happens on timeout/failure, or output format. The security hint is vague and insufficient for a powerful execution tool.

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 that front-loads the core purpose. Every word earns its place - 'execute' (action), 'shell commands' (resource), 'multi-level security' (key differentiator). No wasted words or redundant information.

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 powerful 9-parameter execution tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'multi-level security' means in practice, doesn't describe return values or error behavior, and provides minimal context about execution environment. The combination of high complexity (shell execution) and missing structured data requires more descriptive content.

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 9 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema - it doesn't explain how 'securityLevel' relates to 'multi-level security', or provide examples of command/args usage. With complete schema coverage, baseline 3 is appropriate.

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 'Execute shell commands with multi-level security' clearly states the verb ('execute') and resource ('shell commands'), and the 'multi-level security' qualifier provides some differentiation from sibling tools like 'shell' (which lacks security mention). However, it doesn't explicitly distinguish from other execution-related siblings like 'batch_operations' or 'transaction'.

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 when to choose this over the simpler 'shell' tool, or when to use 'batch_operations' for multiple commands instead. The 'multi-level security' hint implies security-sensitive contexts but lacks explicit when/when-not guidance.

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