AI FileSystem MCP

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

No annotations are provided, so the description carries full burden. It lists actions but doesn't disclose behavioral traits like: whether 'create' requires a base branch, if 'delete' is reversible, permissions needed, or rate limits. The description is minimal and lacks critical context for safe and effective use, especially for destructive operations like delete.

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 concise with a single phrase, but it's under-specified rather than efficiently informative. It front-loads the core actions but lacks necessary detail, making it somewhat wasteful in context. However, it's not verbose or poorly structured.

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 complexity (7 parameters, no annotations, no output schema, includes destructive actions), the description is incomplete. It doesn't cover return values, error conditions, or behavioral nuances. For a multi-action Git tool with potential side effects, more context is needed to ensure proper use.

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 documents all 7 parameters well. The description adds no parameter-specific information beyond implying actions (list, create, delete) that map to the 'action' enum. It doesn't explain parameter interactions or provide examples, but with high 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 'List, create, or delete branches' states the general purpose but is vague about scope and resource. It mentions multiple actions without specifying the resource (Git branches) explicitly, though implied. It doesn't distinguish from sibling Git tools like git_checkout or git_status, which also operate on branches but with different purposes.

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 guidance on when to use this tool vs alternatives. For example, it doesn't specify when to use git_branch vs git_checkout for switching branches, or vs git_status for branch status. The description lists actions but provides no context on prerequisites, scenarios, or exclusions.

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