godot_update_node_transform

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

No annotations are provided, so the description carries full burden. It states the tool updates transforms in saved scenes, implying mutation, but lacks critical behavioral details: whether it overwrites or merges transform fields, if it validates node types, what happens on errors (e.g., invalid node path), or if it saves changes automatically. This is inadequate for a mutation tool with zero annotation coverage.

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?

Two concise sentences with zero waste: first states purpose and scope, second clarifies supported node types. It's front-loaded and appropriately sized for the tool's complexity.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral transparency (e.g., error handling, save behavior), doesn't explain return values, and offers minimal usage guidance. Given the complexity of updating scene files, more context is needed to be fully helpful.

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 fully documents all 5 parameters. The description adds no parameter-specific semantics beyond implying 'transform' is for updates. Baseline 3 is appropriate as the schema does the heavy lifting, but the description doesn't compensate with extra context like format examples for 'transform'.

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 ('Update the transform section') and target ('specific node in a saved scene'), with specificity about supported node types (Node2D, Node3D, Control). It distinguishes from siblings like 'godot_get_node_transform' (read vs. write) and 'godot_edit_scene' (general vs. transform-specific), but doesn't explicitly contrast with all siblings.

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?

Usage is implied through context: it's for updating transforms in saved scenes, with sibling 'godot_get_node_transform' suggesting this is the write counterpart. However, no explicit guidance on when to use this vs. alternatives like 'godot_edit_scene' or prerequisites (e.g., scene must exist) is provided.

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