Godot MCP Bridge

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

With no annotations provided, the description carries the full burden but only discloses that the operation is recursive. It fails to explain what 'Compatibility tool' implies for behavior, what the return structure looks like (file paths? tree nodes?), or whether the operation is read-only or has side effects.

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 appropriately brief and front-loaded with the core action. However, the parenthetical '(Compatibility tool)' adds opacity without sufficient context, and the second sentence could have been used to explain parameters given the lack of schema documentation.

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 zero schema description coverage, no output schema, and no annotations, the description is severely incomplete. A filesystem recursion tool requires explanation of return format, depth limits, filtering mechanisms, and the specific 'compatibility' behavior it provides.

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 0%, requiring the description to compensate. While it mentions 'optional filters,' it does not explain how to use them (likely via additionalProperties), nor does it clarify the semantics of timeoutMs or autoConnect. The mismatch between 'filters' mentioned and the connection/timeout parameters in the schema creates confusion.

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 states a specific action ('Get recursive file tree') that clearly distinguishes this from sibling tools like get_scene_tree or get_game_scene_tree by specifying 'filesystem' and 'recursive'. However, the parenthetical '(Compatibility tool)' is vague and doesn't clarify what compatibility means.

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 mentions 'optional filters' but provides no guidance on when to use this tool versus alternatives like search_files or get_scene_tree. The 'Compatibility tool' label hints at specific use cases but fails to explain when this should be preferred or avoided.

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