Godot MCP Bridge

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

No annotations provided, so description carries full disclosure burden. Fails to mention critical behavioral aspects: file overwrite behavior, what 'autoConnect' implies for the creation flow, required additional properties (given additionalProperties: true), or return values. 'Compatibility tool' is unexplained.

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?

Extremely brief (two sentences), but the second sentence '(Compatibility tool)' wastes space without explanatory value. Given the severe underspecification elsewhere, this brevity is inadequate rather than efficient.

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?

Severely incomplete for a file-mutation tool with no output schema, no annotations, and 0% parameter documentation. Fails to address the additionalProperties: true schema feature which is likely central to the tool's operation (presumably for script content/path).

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 coverage is 0% and description completely fails to compensate. Does not explain timeoutMs (is this for creation timeout or compilation?), autoConnect (connect to what?), or the critical additionalProperties pattern which likely accepts file path and content parameters essential for script creation.

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?

States basic verb and resource ('Create a script file') but lacks specificity about script type, file location, or content. The '(Compatibility tool)' parenthetical hints at legacy status but doesn't clarify scope or distinguish sufficiently from sibling tools like attach_script or create_resource.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., attach_script for attaching to nodes, edit_script for modifying existing files). The 'Compatibility tool' label suggests deprecation or legacy use but fails to specify the preferred alternative.

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