godot-mcp-pilot

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the project runs in debug mode and background, and console logs require a separate tool ('get_debug_output'). However, it lacks details on permissions, error handling, or runtime effects, which are important for a tool that executes projects.

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 front-loaded with the core purpose in the first sentence, followed by an optional feature and a related tool reference. Every sentence adds value without redundancy, making it efficient and well-structured.

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 runs projects with no annotations and no output schema, the description is adequate but incomplete. It covers the basic operation and log retrieval but lacks details on success/failure responses, runtime behavior, or integration with other tools like 'stop_project'.

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 100%, so the schema already documents both parameters. The description adds minimal value by mentioning the optional scene parameter but does not provide additional syntax or format details beyond what the schema specifies.

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 specific action ('run a Godot project in debug mode (background)') and resource ('Godot project'), distinguishing it from sibling tools like 'launch_editor' or 'run_gdscript'. It explicitly mentions the optional scene parameter, which adds specificity.

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 provides clear context for when to use this tool ('run a Godot project in debug mode') and references an alternative tool ('get_debug_output') for retrieving logs. However, it does not explicitly state when not to use it or compare it to other run-related tools like 'stop_project'.

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