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. While 'perform a comprehensive security audit' implies a read-only analysis operation, it doesn't specify what the audit entails, whether it requires special permissions, what kind of output to expect, or if it has any side effects. This leaves significant gaps for a security 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 states the tool's purpose without unnecessary words. It's appropriately sized for a tool with no parameters and gets straight to the point.

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 security audit tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'comprehensive security audit' means, what aspects are checked, what format the results take, or any prerequisites. Given the complexity implied by 'security audit' and the lack of structured data, more detail would be needed for an agent to use this effectively.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of parameters. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. The baseline for 0 parameters with complete schema coverage is 4.

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 action ('perform a comprehensive security audit') and the target resource ('on a directory'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'scan_secrets' or 'analyze_code', which might have overlapping security-related functionality.

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 are several sibling tools that might be relevant for security or directory operations (e.g., 'scan_secrets', 'analyze_code', 'list_directory'), but the description doesn't mention any of them or provide context about when this audit tool is appropriate.

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