game_get_node_info

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

No annotations are provided, so the description carries full burden. It merely states what info is retrieved but does not disclose behavioral traits such as read-only nature, performance impact (e.g., for large node hierarchies), or any prerequisites like scene being instantiated.

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 concise (9 words) and uses a colon-separated list to organize output categories. It is front-loaded and efficient, but could be slightly more structured (e.g., 'Returns the node's class, properties, ...').

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?

The description lists what information is returned but does not specify the output format or structure, especially given the absence of an output schema. It is adequate but could provide more detail on how the data is presented.

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% (nodePath is described with example). The tool description does not add any additional meaning beyond the schema, so baseline 3 applies.

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's purpose: 'Get node info: class, properties, signals, methods, children'. It specifies the verb 'get' and resource 'node info', and lists the exact information retrieved, which distinguishes it from siblings like 'get_property' or 'list_signals'.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., get_property for a single property, list_signals for signals only). It does not mention context or when not to use it.

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