godot_instance

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

No annotations provided; the description lists actions including destructive ones (terminate) but does not elaborate on side effects or requirements.

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 concise (one sentence) and front-loaded with the key verb 'Manage', though it could be slightly more structured with clearer separation of actions.

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 multi-action nature and existence of an output schema, the description covers the basics but lacks details on return values or per-action behavior.

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 coverage is 0%, but the description adds meaning by naming actions and indicating that launch_editor and adopt require a project_path parameter, compensating for the generic schema.

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 tool manages Godot EDITOR instances and lists specific actions (launch_editor, list, switch, terminate, adopt), distinguishing it from sibling tools like godot_editor_read or godot_scene.

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 through listed actions but does not explicitly state when to use this tool versus alternatives or provide usage conditions.

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