godot_interact_node

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

The annotations only indicate this is not a read-only, non-idempotent, and not-destructive operation; the description adds little beyond naming the action kinds. It does not mention that typing may modify node text, that clear_before_type may wipe existing content, that drag/drop needs viewport coordinates, or that interactions can change application state.

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 one short sentence with no filler and the main action verbs are front-loaded. It is not penalized heavily for brevity here, but it loses a point because it gives an informal action label instead of the actual schema vocabulary.

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 supports multiple interaction modes, coordinate-based drag/scroll, and possible text mutation, this description is too thin to be a complete guide. It does not mention runtime state effects, required node type, coordinate system, or differences from sibling tools. The output schema helps with return values, but the broader usage context is missing.

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?

With schema description coverage reported as 0%, the description does almost nothing to explain parameters such as node_path, text, scroll_delta, drag_to_position, or action values. It also uses the label 'drag_to' while the schema action is named 'drag_and_drop', which could create ambiguity for an agent choosing parameters.

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 performs interaction actions (click, type_text, drag_to, scroll) on a located node, so an agent can understand the basic purpose. It is not a full match to the schema's action set, and it does not distinguish itself from related node tools, but the core verb and resource are specific.

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?

There is no guidance about when to use this tool instead of alternatives like godot_simulate_input, godot_focus_node, or godot_set_editor_selection. The phrase 'on a located node' only implies a node should already exist, but it does not explicitly state prerequisites, workflow order, or when not to use this tool.

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