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 of behavioral disclosure, yet reveals nothing about side effects (disk persistence), safety (backup/undo capabilities), or return values. The cryptic '(Compatibility tool)' label suggests special behavior that is left completely undocumented.

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?

While brief at only four words, this constitutes under-specification rather than efficient conciseness. The '(Compatibility tool)' tag consumes space without explanation, and the front-loading provides no actionable detail about the edit operation's nature.

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 tool that presumably performs file mutation (high complexity), the description is inadequate. With zero schema coverage, no annotations, no output schema, and unexplained parameters, the agent lacks sufficient information to invoke the tool correctly or safely.

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 input schema has 0% description coverage, and the description fails to compensate by explaining the purpose of 'timeoutMs' and 'autoConnect' parameters. These parameters suggest network or process-communication behavior (likely connecting to the Godot editor), which is critical context for a file-editing tool but is entirely absent from the description.

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 the core verb ('Edit') and resource ('shader file'), but is vague about the scope of editing (content vs. metadata) and fails to differentiate from siblings like 'create_shader', 'read_shader', or 'set_shader_param'. The parenthetical '(Compatibility tool)' is unexplained jargon that adds no 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?

No guidance is provided on when to use this tool versus alternatives such as 'set_shader_param' (for material parameters) or 'create_shader' (for new files). There are no stated prerequisites, such as whether the shader file must already exist, or warnings about potential overwrites.

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