Godot MCP Bridge

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

No annotations provided, so description carries full burden. It hints at destructive vs. overwrite behaviors via 'replace/full content' but fails to disclose side effects, error handling, what 'Compatibility tool' implies for behavior, or persistence guarantees.

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 (one sentence + parenthetical), but the '(Compatibility tool)' annotation is opaque—unclear if this signals deprecation, legacy support, or specific behavior. Information-to-word ratio is mediocre due to this unexplained qualifier.

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?

Inadequate for a script-editing tool with zero schema documentation and no output schema. Missing critical details: how to specify the target script, content format, encoding, or return value structure. The additionalProperties pattern (common in Godot MCP tools) is not explained.

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 has 0% description coverage and accepts additionalProperties (likely for script content), yet the description fails to document timeoutMs/autoConnect or explain how to pass content parameters. The 'replace or full content' phrase hints at payload semantics but lacks concrete parameter mapping.

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 the tool edits scripts and specifies two distinct modes (replace vs full content), distinguishing it from siblings like create_script, read_script, and validate_script. However, it doesn't explain what 'Compatibility tool' means, slightly diluting clarity.

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?

Mentions 'replace or full content' implying two usage modes, but provides no explicit guidance on when to use this tool vs. create_script, when to choose replace over full content, or prerequisites like script existence.

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