Godot MCP

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. It mentions 'capture output', which hints at a read operation, but doesn't specify what kind of output (e.g., logs, errors, performance data), whether it's a blocking or non-blocking call, or any side effects like resource consumption or project state changes. This leaves significant gaps for a tool that likely involves execution and monitoring.

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 extremely concise with a single, direct sentence that front-loads the core action ('run the Godot project') and adds a key detail ('capture output'). There is no wasted verbiage, making it efficient and easy to parse.

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 the complexity of running a project (which likely involves execution, monitoring, and output handling), the description is incomplete. With no annotations and no output schema, it fails to explain critical aspects like what the captured output includes, error handling, or how the tool interacts with sibling tools (e.g., 'stop_project'). This makes it inadequate for safe and effective use by an AI agent.

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 schema description coverage is 100%, so the schema already documents both parameters ('projectPath' and 'scene') with clear descriptions. The tool description doesn't add any additional meaning or context about the parameters beyond what's in the schema, such as example paths or scene formats, but this is acceptable given the high schema coverage.

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 clearly states the action ('run') and target ('Godot project'), with the additional detail of 'capture output' specifying what the tool does beyond just execution. However, it doesn't explicitly differentiate from sibling tools like 'launch_editor' or 'stop_project', which would require more specific comparison.

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. For example, it doesn't clarify when to use 'run_project' versus 'launch_editor' or how it relates to 'stop_project'. The description lacks context about prerequisites or typical use cases.

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