game_get_scene_tree

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

Annotations provide no hints (no readOnlyHint or destructiveHint). The description adds no behavioral details beyond the name itself—e.g., it does not state that this is a read-only operation, that it returns the full tree or a subset, or whether it works only on running games. This lack of disclosure leaves the agent uninformed about invocation consequences.

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 a single, clear sentence with no wasted words. It is front-loaded and efficient. However, it could be slightly expanded to include output details without becoming verbose, so it is concise but not maximally informative.

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 complexity (no parameters, no output schema), the description is minimally viable. It conveys the basic purpose but omits details about the structure of the returned scene tree (e.g., node hierarchy, properties). An agent would need additional context to fully utilize the output.

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?

The input schema has zero parameters, and schema description coverage is trivially 100%. With no parameters to describe, the baseline score is 4. The description provides no additional parameter information, which is acceptable given the absence of 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 gets the scene tree structure of the running game, using a specific verb ('Get') and resource ('scene tree structure'). However, it does not differentiate from sibling tools like 'godot_scene_tree' or 'manage_scene_structure', which may have overlapping functionality.

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?

No usage context is provided. The description does not specify when to use this tool versus alternatives, nor does it mention any prerequisites or side effects. The agent receives no guidance on optimal invocation scenarios.

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