Game Get Scene Tree

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

The annotations already declare readOnlyHint and idempotentHint as true, and destructiveHint as false, so the description adds no additional behavioral context. It does not disclose what the returned tree includes (e.g., all nodes, only visible nodes) or any side effects.

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 very short (one truncated sentence) but front-loads the key action. However, the truncation reduces clarity, and it could be more complete without adding length.

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?

Despite having an output schema, the description lacks context about the returned structure (e.g., whether it returns the entire hierarchy or just a subset). For a tool that retrieves a tree, more details would help the agent understand the output format and scope.

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 100% coverage with a description for the only parameter maxNodes, so the description does not need to add much. It provides no extra semantics beyond the schema, such as default behavior or how the limit affects results.

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 states 'Get scene tree structure of the runn…' which clearly identifies the tool's purpose as retrieving the hierarchy of the game scene. It is specific enough to distinguish from sibling tools like game_get_node_info which returns details of a single node.

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 guidance is provided on when to use this tool versus alternatives such as game_get_ui or game_get_node_info. The description does not mention any prerequisites, context, or exclusions.

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