godot_get_node_transform

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool reads data (implying non-destructive, read-only behavior) and specifies supported node types, which adds some context. However, it lacks details on permissions, error handling, performance, or output format (e.g., what the transform data looks like), leaving gaps for a mutation-adjacent tool in a development context.

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 concise sentences with zero waste: the first states the core purpose and scope, and the second adds crucial constraint information (supported node types). It's front-loaded with the primary action and efficiently covers necessary details without 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 no annotations and no output schema, the description is moderately complete for a read operation: it specifies the action, target, and supported types. However, it lacks details on return values (critical without an output schema), error cases, or integration with sibling tools, leaving the agent to infer behavior in a complex toolset. This is adequate but has clear gaps.

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 four parameters (project_path, scene_path, node_path, godot_executable). The description adds no parameter-specific information beyond what's in the schema, such as examples or constraints on node_path for supported types. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Read the transform section') and target ('a specific node in a saved scene'), with specificity about supported node types (Node2D, Node3D, Control). It distinguishes from siblings like 'godot_get_node_properties' (which reads properties generally) and 'godot_update_node_transform' (which modifies transforms). However, it doesn't explicitly contrast with these siblings in the text itself, preventing a perfect score.

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 by the description's focus on reading transforms for specific node types in saved scenes, suggesting it's for inspection rather than modification. However, there's no explicit guidance on when to use this versus alternatives like 'godot_get_node_properties' for other properties or 'godot_get_scene_tree' for broader scene data. No prerequisites or exclusions are mentioned.

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