Control the Godot editor

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

With no annotations provided, the description carries the full burden. It discloses the bridge_install requirement and the fact that it can launch the editor, which is useful, but it does not detail side effects (e.g., save overwriting files, play/stop affecting the running project) or error behavior. It provides some behavioral context but not comprehensive disclosure.

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 two sentences, front-loaded with the core function, then a compact list of actions and a prerequisite. Every phrase earns its place, with no redundancy.

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 tool has multiple actions, no output schema, and no annotations, the description provides a solid overview of the action space, but it omits a couple of enum values (reload_scene, state specifics) and return/error expectations. Still, for a control tool with a self-explanatory enum, it is reasonably complete.

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?

All parameters already have descriptions in the schema (100% coverage), so the baseline is 3. The description's list of actions loosely maps to the action enum but does not add new meaning beyond what the schema provides.

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 opens with a specific verb-resource pair ('Drive a running Godot editor') and enumerates concrete capabilities (open scene, save, play/stop, select nodes, rescan), which clearly distinguishes it from sibling tools like run_project or scene_tree. The additional note about launching the editor further clarifies its scope.

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 implies usage for controlling a Godot editor and notes the bridge_install prerequisite, but it does not explicitly contrast with alternative tools or state when not to use it. It offers context but no exclusions or direct sibling comparisons.

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